Skip to main content
Glama

sellfox_ads_sp_campaign_hourly

sellfox_ads_sp_campaign_hourly

Get hourly performance data for Amazon Sponsored Products ad campaigns. Analyze trends minute-by-minute for the last 60 days.

Instructions

小时报告-SP广告活动报告。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shopIdYes店铺ID(单店)
campaignIdYes广告活动ID
reportDateYes报告日期 yyyy-MM-dd,限最近60天
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, rate limits, or what data the hourly report contains (e.g., metrics like impressions, clicks). The description carries the full burden but fails to convey key behavioral context.

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

Conciseness3/5

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

The description is very concise (one short phrase), but it sacrifices necessary detail for brevity. While it fits in a single line, it omits important information about output or usage, making it acceptable but not efficient in conveying value.

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

Completeness2/5

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

Given the tool has three required parameters and no output schema, the description should provide more context about what the hourly report contains (e.g., metrics, time granularity). The current description is incomplete, leaving the agent without key information about the tool's output.

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?

The input schema has 100% coverage with descriptions for all three parameters (shopId, campaignId, reportDate). The description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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?

The description clearly states it is an hourly report for SP ad campaigns, specifying the resource and type of report. However, it does not differentiate from many sibling tools that are also hourly reports for different levels (e.g., ad groups, targets), missing a chance to uniquely identify its purpose.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The sibling list includes many similar hourly report tools, but the description offers no context, exclusions, or comparisons to help the agent choose correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shuolol/sellfox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server