nexscope_amazon_ads_sp_insights_report_statusUses existing Amazon Ads authorization and tokenized download handling. Create once, poll by reportId, then download using a documentToken.
| Name | Required | Description | Default |
|---|---|---|---|
| reportId | Yes | ||
| connectionId | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the read-only annotations, the description provides critical technical behavioral context: it uses 'existing Amazon Ads authorization' and 'tokenized download handling.' This informs the agent about the system's operational state and security protocol.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is highly concise and front-loaded. It uses minimal wording to define the three stages of the overall process (create, poll, download), making every sentence essential.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that the tool is part of a complex, asynchronous workflow (creation followed by polling), outlining this entire lifecycle is necessary for functional completeness. It bridges the gap between 'creation' and 'download' steps effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Since schema description coverage is 0%, the description must carry the semantic load. It clarifies the role of 'reportId' (the object to poll) within the workflow. It doesn't add deep semantic meaning to the types, but it provides essential context for usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The tool name, title, and description precisely define its role in managing the status of an Amazon Ads SP Insights report. It explicitly functions as a 'poller', clearly distinguishing it from tools that initiate reports or complete downloads.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear operational context by outlining the multi-step workflow: first create, then poll this tool via reportId, and finally download. This guides the user on exactly when this tool fits into the larger process.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.