Skip to main content
Glama

Target product questions

run_target_products_questions
Read-onlyIdempotent

Customer questions and their answers for a Target product by TCIN or URL. 1 point per returned record.

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": {
      "product": "<product>"
    },
    "name": "run_target_products_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesTCIN or product URL. e.g. 86216189
max_itemsNoMax items (up to 500) Default: 25.
start_pageNoStarting page Default: 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so safety is covered. The description adds a genuinely useful non-obvious detail — '1 point per returned record' (cost/credits) — but says nothing about pagination behavior or return shape.

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?

Two tight sentences with the core capability front-loaded and the cost note appended. No filler; every clause carries information.

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 simple 3-parameter read tool with complete schema coverage and full annotation hints, the description covers what is returned (questions + answers), the keying input, and cost. No output schema exists, but the omission of return-format detail is minor at this complexity.

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 description coverage is 100%, so all three parameters (product, max_items, start_page) are already documented with examples and defaults. The description only restates 'TCIN or URL', adding no syntax or format detail beyond the schema. Baseline 3 applies.

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+resource: retrieving customer questions and their answers for a Target product, keyed by TCIN or URL. This clearly distinguishes it from siblings like run_target_products_reviews and run_target_products_recommendations, though it never names them explicitly.

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?

The resource 'customer questions and answers' implies when to use it (Q&A retrieval for a known Target product), but there is no explicit when-to-use/when-not guidance and no mention of alternatives like the reviews tool. Usage is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources