Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

target_questions

Retrieve Target product questions and answers by numeric tcin, including author, votes, and nested replies, with pagination using page and per_page.

Instructions

List Target product questions and answers. Lists customer questions for a Target item given by its numeric tcin, each with its text, author, submission time, helpful votes and nested answers. page is zero-based and per_page runs 1 to 25. The response gives total_pages and count for paging.

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page
tcinYesNumeric Target item id
per_pageNoQuestions per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose meaningful behavior: the operation is read-only in nature, each question carries text/author/submission time/helpful votes/nested answers, per_page is bounded 1–25, and the response exposes total_pages and count for paging. It omits auth requirements and rate limits, which is the main remaining gap.

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?

Three sentences, zero filler, and the scope (which item) and content shape are front-loaded before the paging details. Every sentence adds a distinct fact.

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?

With no output schema and no annotations, the description partially compensates by describing returned question fields and paging metadata. For a simple read-only list tool with full schema coverage this is nearly complete; only permissions/error behavior is unaddressed.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value the schema lacks: the concrete `per_page` range of 1 to 25 (schema only says 'Questions per page'). It also restates tcin as a numeric Target item id, though the zero-based page note duplicates the schema.

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

Purpose4/5

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

States a specific verb and resource ('List Target product questions and answers') and scopes it to a Target item identified by `tcin`. It is distinguishable from target_reviews by the questions/answers framing, but it never names the sibling tools (e.g. other *_product_questions tools or target_reviews), so differentiation is by inference only.

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

Usage Guidelines3/5

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

Usage is implied: you need a `tcin` for a Target item and want its customer Q&A. There is no explicit when-to-use vs. when-not guidance and no alternative named (target_reviews, target_product, other retailers' question tools). Adequate but leaves routing to the agent.

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