Sumhound — e-commerce platform changes & seller deadlines

get_platform_changes

Read-only

List recent seller-facing changes on Amazon, Shopify and/or TikTok Shop, newest first.

Use for "what changed on TikTok Shop recently", "any new Amazon fees",
"Shopify API updates this month". Each change is curated from the
platform's official changelog/announcement and includes a summary, change
type, impact types, effective date and the original source URL.

Args:
    platform: Optional platform slug — amazon, shopify or tiktok-shop.
        Empty = all platforms.
    limit: Max changes to return, 1-100 (default 10).

Returns {generated_at, source, platforms, total, changes:[{id, platform,
publishedAt, title, summary, changeType, topics, impactTypes, effectiveAt,
deadline, originalUrl}]}. Cite each record's originalUrl when presenting;
mention generated_at if freshness matters.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`platform`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it states changes are curated from official changelogs, includes specific fields like summary and impact types, and instructs to cite originalUrl when presenting and mention generated_at for freshness. This goes beyond annotations and provides actionable guidance.

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

Conciseness5/5

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

The description is well-structured and appropriately sized. It front-loads the core purpose in the first sentence, provides usage examples, then details parameters and return format in a clear, scannable manner. Every sentence adds value; no wasted words.

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

Completeness5/5

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

Given the tool's moderate complexity (two optional params), the description is complete. It explains the output format in detail (fields returned), provides usage guidance, parameter semantics, and behavioral notes (citing originalUrl, freshness). The sibling tool's purpose is implicitly clear from the name; no further context needed.

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

Parameters4/5

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

The schema provides two parameters (limit, platform) with defaults but no descriptions. The tool description compensates well: it explains platform is an optional slug (amazon, shopify, tiktok-shop) and empty means all platforms; limit is a max limit of 1-100 with default 10. This adds meaning beyond the bare schema, though the absence of enums in schema is mitigated by explicit slug examples.

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

Purpose5/5

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

The description clearly states the tool lists recent seller-facing changes across three named platforms (Amazon, Shopify, TikTok Shop), newest first. It distinguishes itself from the sibling get_upcoming_deadlines by focusing on past changes rather than upcoming deadlines, and explicitly names the platforms, making purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides clear usage examples like "what changed on TikTok Shop recently" and "any new Amazon fees", effectively signaling when to use this tool. However, it does not explicitly state when not to use it or contrast with get_upcoming_deadlines, though the purpose naturally differentiates them.

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

All Sumhound — e-commerce platform changes & seller deadlines tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

The two tools have clearly distinct purposes: one lists platform changes, the other lists upcoming deadlines. There is no overlap in functionality, and the descriptions make the difference explicit.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern ('get_platform_changes', 'get_upcoming_deadlines'), with 'get' as the verb and clear domain-specific nouns. The naming is predictable and uniform.

Tool Count5/5

With only two tools, the set is lean and precisely scoped to the server's purpose of tracking platform changes and deadlines. No unnecessary tools, and the count is appropriate for the domain.

Completeness5/5

The two tools cover the core needs of the domain: retrieving platform changes and retrieving upcoming deadlines. The descriptions indicate they handle all relevant platforms and provide necessary details, leaving no obvious gaps.

Resources

Need Help?