AI Content Generation

Product Description Generator MCP

Generate product descriptions from writing instructions and product images. Call the Product Description Generator API via REST or MCP with a Nexscope API key.

CostRecent 10 credits / callOnline Test

Product Description Generator AI Prompts & Use Cases

After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.

New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.

1. Write A Product Description

Prompt: Write a product description from [verified product facts], following [tone and audience brief]. Use [supported text model] with [supported reasoning level] and no reference images for this text-only draft.

2. Write Copy From Product Media

Prompt: Write a description from [product brief] and [reference images or reference video], using [supported model and reasoning level]. Do not infer specifications that the media cannot establish.

3. Retrieve An Existing Copy Draft

Prompt: Check the existing copy-generation task [task ID]. Show the completed text if available; if it is still processing, keep that task rather than creating another draft.

What You Need to Provide

Provide assets you may use and that meet this tool’s documented file, dimension and count limits.

A pending task is not a completed image, video or text result. Retrieve the existing task rather than submitting a duplicate.

Step 1 · Connect

Connect Your AI Assistant

Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json

Authentication

Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Using an API key? Get your key from API Access and include it in the Authorization header shown above.

Call this MCP tool

MCP tool name

nexscope_product_description_generator

MCP endpoint

https://api.nexscope.ai/mcp

JSON-RPC method

tools/call

Initialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.

{
  "jsonrpc": "2.0",
  "id": "product-description-generator-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_product_description_generator",
    "arguments": {
      "imageUrls": [],
      "model": "GEM_3_FLASH",
      "operation": "create",
      "prompt": "Write a product description for a wireless speaker.",
      "thinkingLevel": "minimal"
    }
  }
}

MCP 2025-11-25 · Streamable HTTP

Progress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.

Arguments

Name	Type	Required	Description
`operation`	`string`	optional	create (default) or query. Example: create
`prompt`	`string`	optional	Product-copy generation instruction; required by create. Example: Write a product description for a wireless speaker.
`imageUrls`	`array`	optional	Media URLs used as context. Pass an empty array for text-only generation; use up to 10 images or typically one video. Example: []
`thinkingLevel`	`string`	optional	Reasoning level required by create. GEM_3_1_PRO does not support minimal. Example: minimal
`model`	`string`	optional	Text-generation model. GEM_3_FLASH is the default. Example: GEM_3_FLASH
`memberId`	`string`	optional	Optional provider member identifier used by create and query. Example:
`taskId`	`string`	optional	Provider task ID returned by create; required by operation=query. Example: 123456789

Response fields

Treat structuredContent as the programmatic API response payload.

Name	Type	Required	Description
`code`	`integer`	required	0 means accepted or successful; nonzero is a platform error.
`cost`	`string`	required	Elapsed milliseconds, never credits; -1 outside web requests.
`data`	`any`	required	Data value used by this API operation.
`msg`	`string \| null`	required	Msg value used by this API operation.
`time`	`string`	required	Server local time: yyyy-MM-dd HH:mm:ss.
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds.

Any of option 1

Name	Type	Required	Description
`data`	`object`	required	Data value used by this API operation.
`data.completionTokens`	`integer`	optional	Output token count when the task succeeds. Example: 350
`data.content`	`string`	optional	Generated product copy when the task succeeds. Example: Example product description.
`data.costTime`	`integer`	optional	Execution time reported by the upstream provider. Example: null
`data.costToken`	`integer`	optional	Provider-reported token cost. Example: 1
`data.dataSnapshotMonth`	`string`	optional	Data snapshot month returned by the upstream provider. Example: null
`data.page`	`integer`	optional	Current page returned by the upstream provider. Example: null
`data.pageItemCount`	`integer`	optional	Item count on the current page returned by the upstream provider. Example: null
`data.pageSize`	`integer`	optional	Page size returned by the upstream provider. Example: null
`data.promptTokens`	`integer`	optional	Input token count when the task succeeds. Example: 120
`data.sourceTool`	`string`	optional	Provider-specific source tool name. Example: null
`data.sourceType`	`string`	optional	Provider-specific source platform type. Example: null
`data.status`	`string`	optional	Task status such as PROCESSING, SUCCESS, or FAILED. Example: PROCESSING
`data.taskId`	`string`	optional	Asynchronous generation task ID. Example: 123456789
`data.title`	`string`	optional	Provider-specific response title. Example: null
`data.totalPage`	`integer`	optional	Total page count returned by the upstream provider. Example: null
`data.totalTokens`	`integer`	optional	Total token count when the task succeeds. Example: 470
`data.type`	`string`	optional	Provider-specific render or payload type. Example: null

Any of option 2

Name	Type	Required	Description
`data`	`null`	required	Data value used by this API operation.

Example Q&A

Based on a published documentation sample, not a live tool call.

Your Question

Retrieve the existing copy-generation task 2549906.

Example Answer

The sample reports a successful task whose content says the supplied product description lacks usage instructions. It returns no usage steps. This is a completed text response, not evidence that missing instructions were found elsewhere.

About this sample: Excerpt of a published documentation sample, not current data or a live tool call. Full source data is preserved in the published sample; arrays and long text may be shortened here. Business values are preserved from the published sample; required outer timing and trace metadata are illustrative placeholders because the published source omits them.

View the Published Sample Data (JSON)

Published REST data example. Use Parameters & Response for MCP arguments when calling this tool.

Data Example

Sample request and response

Request parameters

{
  "operation": "query",
  "taskId": "2549906"
}

Response

{
  "code": 0,
  "msg": null,
  "data": {
    "promptTokens": 441,
    "taskId": "2549906",
    "content": "```json\n{\n  \"sufficient\": false,\n  \"steps\": [],\n  \"missingInstructions\": \"Ürün açıklamasında ürünün özellikleri, faydaları ve hangi köpek türleri için uygun olduğu belirtilmiş; ancak ürünün nasıl kullanılacağına dair (örneğin: kullanım sıklığı, temizleme talimatı veya gözetim altında tutulması gibi) herhangi bir uygulama adımı veya kullanım talimatı bulunmamaktadır.\"\n}\n```",
    "completionTokens": 97,
    "status": "SUCCESS",
    "points": 0
  }
}

View the MCP Request & Response Format

Examples

Based on a published documentation sample, not a live tool call.

The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.

MCP Request

{
  "jsonrpc": "2.0",
  "id": "product-description-generator-example",
  "method": "tools/call",
  "params": {
    "name": "nexscope_product_description_generator",
    "arguments": {
      "operation": "query",
      "taskId": "2549906"
    }
  }
}

MCP Response Format

{
  "jsonrpc": "2.0",
  "id": "product-description-generator-example",
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"code\":0,\"msg\":null,\"data\":{\"taskId\":\"2549906\",\"content\":\"```json\\n{\\n  \\\"sufficient\\\": false,\\n  \\\"steps\\\": [],\\n  \\\"missingInstructions\\\": \\\"Ürün açıklamasında ürünün özellikleri, faydaları ve hangi köpek türleri için uygun olduğu belirtilmiş; ancak ürünün nasıl kullanılacağına dair (örneğin: kullanım sıklığı, temizleme talimatı veya gözetim altında tutulması gibi) herhangi bir uygulama adımı veya kullanım talimatı bulunmamaktadır.\\\"\\n}\\n```\",\"status\":\"SUCCESS\"},\"cost\":\"-1\",\"time\":\"2026-01-01 00:00:00\",\"traceId\":null,\"ts\":\"0\"}"
      }
    ],
    "structuredContent": {
      "code": 0,
      "msg": null,
      "data": {
        "taskId": "2549906",
        "content": "```json\n{\n  \"sufficient\": false,\n  \"steps\": [],\n  \"missingInstructions\": \"Ürün açıklamasında ürünün özellikleri, faydaları ve hangi köpek türleri için uygun olduğu belirtilmiş; ancak ürünün nasıl kullanılacağına dair (örneğin: kullanım sıklığı, temizleme talimatı veya gözetim altında tutulması gibi) herhangi bir uygulama adımı veya kullanım talimatı bulunmamaktadır.\"\n}\n```",
        "status": "SUCCESS"
      },
      "cost": "-1",
      "time": "2026-01-01 00:00:00",
      "traceId": null,
      "ts": "0"
    },
    "isError": false
  }
}