tool4seller-mcp

Diagnose ad efficiency

diagnose_ad_efficiency

Read-only

Diagnoses advertising efficiency with read-only advertising metrics for one store and business date range. MCP reporting and workflow metric date ranges use yyyy-MM-dd and include both startDate and endDate, with at most 95 calendar days per range. For longer read-only reports, split into non-overlapping windows: endDate = startDate plus 94 days, capped at the requested end date; the next startDate is the previous endDate plus 1 day. Apply the same limit independently to comparison ranges. Do not average ratios such as ACOS or ROAS across windows; recompute them from summed base metrics. Do not automatically split advertising write plans or metric-based selectors; obtain a supported analysis window from the user. Keyword ranking trends have separate limits: DAILY supports up to 90 inclusive days and RAW up to 31 inclusive days. For keyword ranking trends, use these interval-specific limits when splitting read-only reports. This reporting limit does not apply to campaign scheduling dates.

Input Schema

Name	Required	Description
`focus`	No	Optional focus such as sales, profit, ads, or inventory.
`endDate`	Yes	Business end date in yyyy-MM-dd format. The inclusive range can contain at most 95 days.
`storeId`	Yes	Store identifier, in sellerId:marketplaceId format.
`startDate`	Yes	Business start date in yyyy-MM-dd format. The inclusive range can contain at most 95 days.
`compareEndDate`	No	Optional comparison end date in yyyy-MM-dd format. The comparison range independently allows at most 95 inclusive days.
`compareStartDate`	No	Optional comparison start date in yyyy-MM-dd format. The comparison range independently allows at most 95 inclusive days.

Output Schema

Name	Required	Description	Default
`scope`	No
`metrics`	No
`summary`	No
`evidence`	No
`findings`	No
`warnings`	No
`workflow`	No
`nextQueries`	No
`recommendedActions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond annotations with concrete rate limits (95-day range), splitting rules, and aggregation caveats (do not average ratios), plus exceptions for write plans and keyword ranking trends. Annotations already confirm read-only, but this description adds critical operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose but then includes lengthy, off-topic instructions about advertising write plans and keyword ranking trends that are irrelevant to this read-only diagnosis tool. These repeated and extraneous sentences dilute the core message.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers calling requirements well (date formats, range limits, splitting), and the output schema handles return values. However, it omits guidance on when to select this vs sibling diagnostic/query tools and contains irrelevant limits that could mislead, leaving a gap for correct tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and schema descriptions already document each parameter, including independent 95-day limits for comparison ranges. The description adds no parameter-specific meaning beyond what the schema provides, so baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb 'Diagnoses' and resource 'advertising efficiency' with scope 'one store and business date range'. It does not explicitly differentiate from sibling tools like query_advertising or diagnose_sales_change, so it misses the top mark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides extensive procedural guidance on date-range splitting and aggregation but never states when to choose this tool over query_advertising or other diagnose_* siblings. Usage is implied by 'read-only advertising metrics' but alternatives are not named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All tool4seller-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?