Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

target_product

Read-only

Fetch item detail data for one Target product by its numeric TCIN, including product content, price, rating, images, and selected-store availability. Use target_search or target_category_products to discover TCINs, or target_reviews and target_questions for customer feedback.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tcin": "<tcin>"
    },
    "name": "target_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
tcinYesRequired. Numeric Target item id (TCIN).
store_idNoOptional. Positive Target store id used for pricing. Defaults to 2885.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds useful scope context ('selected-store availability') but does not disclose rate limits, auth requirements, or error behavior. With annotations carrying the safety profile, this is an adequate but not rich disclosure.

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?

Two sentences with no wasted words. The fetch action and its payload are front-loaded, and the routing guidance is compacted into the second sentence.

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?

For a two-parameter read tool with an output schema (which owns the return-value contract), full schema coverage, and annotations covering safety, the description supplies everything an agent needs: identity, scope, and the discovery path for the required id.

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 tcin and store_id are fully documented in the schema. The description reinforces that the TCIN is numeric and hints that store context ('selected-store availability') matters, but adds no syntax beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 ('Fetch item detail data for one Target product') plus the required identifier ('numeric TCIN'), and enumerates the payload (content, price, rating, images, store availability). An agent can distinguish it from sibling search/category/review tools without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes to the discovery tools ('Use target_search or target_category_products to discover TCINs') and redirects feedback queries to target_reviews/target_questions. Both the when-to-use and the alternatives are named, leaving nothing to inference.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources