Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

yahoo_shopping_author

Fetch a Yahoo Shopping contributor profile and a paginated archive of their articles by author slug; specify page numbers to browse older posts.

Instructions

Yahoo Shopping author profile and article archive. Fetches one Yahoo Shopping contributor profile and a page of the author's article archive. Use the author slug from author_url in /yahoo-shopping/article; page follows Yahoo's path-segment pagination. Article cards may link to sibling publishers such as AOL.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based article archive page, defaults to 1
authorYesYahoo Shopping author slug; use author_url from /yahoo-shopping/article

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add useful context beyond the schema (path-segment pagination and the warning that article cards may link to sibling publishers such as AOL), but it says nothing about permissions, rate limits, or the shape/size of the returned profile and archive page.

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?

Three short sentences, with the purpose front-loaded and the parameter guidance following. The AOL/sibling-publisher note is a slight tangent but still earns its place as a link-following caveat.

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

Completeness4/5

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

For a two-parameter read tool with no output schema, the description explains what is returned (profile plus a page of archive) and how paging works. It leaves the contents of the profile and archive page unspecified, but the essentials for correct invocation are present.

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%, so both parameters are already documented, and the description largely restates the schema's own note that author comes from author_url. The only marginal addition is the pagination model for page, which is useful but thin.

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?

States a specific verb and resource: fetches one Yahoo Shopping contributor profile plus a page of that author's article archive. A reader can distinguish it from yahoo_shopping_article because it returns the author entity and an archive listing, not a single article.

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?

Explicitly says to use the author slug obtained from author_url in /yahoo-shopping/article, which tells the agent how to obtain the required parameter rather than guessing. It also explains that page follows Yahoo's path-segment pagination, though it gives no explicit when-not-to-use or alternative tool.

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

Deploy Server

Other Tools