Product Details
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL of the product to get details for. | |
| region | No | Region the proxy will be set to so you can access products from that country. Use 2 letter country codes like US, GB, FR, etc. For England, don't use UK, use GB. | |
| get_related_videos | No | Whether to get related videos for the product. These are affiliate videos promoting the product. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for disclosing behavior. It discloses nothing about what data is returned, whether this is a read-only operation, any rate limits, or what 'product details' entails. This is a complete absence of behavioral information.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short and front-loaded, but this is under-specification, not conciseness. A useful description would at least state the action and key context; this two-word phrase does not earn its place as a meaningful description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a scraping tool with no output schema, no annotations, and a description that provides zero context. Given the complexity of the domain and the wide array of sibling tools, the description is wholly insufficient for an agent to understand when or how to invoke this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all three parameters: url, region, and get_related_videos. The description adds no additional parameter context, but the baseline of 3 applies because the schema handles the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is simply 'Product Details', which restates the tool name without specifying an action or resource scope. It does not differentiate this tool from the many sibling scraping tools, nor does it say what 'details' means.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. Sibling tools like scrapecreators_shop_products or scrapecreators_product_reviews suggest similar use cases, but no comparison or exclusion is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.