Skip to main content
Glama

sellfox_ads_sd_target_hourly

sellfox_ads_sd_target_hourly

Retrieve hourly performance data for Sponsored Display ad targeting by campaign ID and date. Analyze targeting performance at hourly granularity for up to 60 days.

Instructions

小时报告-SD投放报告。

Input Schema

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

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

No annotations. Description does not disclose data freshness, pagination, timezone, rate limits, or read-only nature. Minimal 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.

Conciseness4/5

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

Single sentence, no wasted words. Appropriate for a simple reporting tool, though could add more detail without being verbose.

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?

No output schema and no description of return values. An hourly report should indicate what metrics are returned (e.g., impressions, clicks, spend). Missing critical context.

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% with clear parameter descriptions. The description itself adds no extra meaning beyond the schema, so baseline 3 applies.

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

Purpose3/5

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

Description says 'Hourly report - SD delivery report' which indicates it's for SD target hourly data, but doesn't explicitly state it's for target-level performance. The tool name includes 'target', but the description is vague.

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 on when to use this tool versus sibling tools like sellfox_ads_sd_campaign_hourly or sellfox_ads_sd_ad_group_hourly. The description provides no context for selection.

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