Skip to main content
Glama
Sign In

Logimu

by com.logimu
OverviewDiscussionsAdmin

list_tracked

Read-onlyIdempotent

LIST the products this API key tracks (track_product): each with its status, interval, read (offers or product_page), expiry, whether the hot lane has picked it up, the lane's last and next read, plus the plan's tracking allowance (snapshots a day: total, used, remaining). USE WHEN the user asks what is being tracked, whether a tracking is live, how much allowance is left, or wants to stop one (the id goes to DELETE /v1/track/{id} on the REST API). Stopped trackings stay listed for 30 days. COST 0 credits. Paid plans only.

Input Schema

NameRequiredDescriptionDefault
asinNoOnly these products: one ASIN or up to 500 comma-separated (2026-10-30).
limitNoMaximum rows to return.
offsetNoRows to skip (paging; total says how many there are).
statusNoOnly trackings in this state (default: all, newest first).
countryNoOnly this marketplace's trackings (default: every marketplace).
events_forNoA tracking id: return that tracking's webhook events instead of the list - which notify_if threshold fired on which observation, the payload, and the delivery state (pending / delivered / failed, attempts, last error).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / asin
      Added value: +{
+  "description": "Only these products: one ASIN or up to 500 comma-separated (2026-10-30).",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint, idempotentHint, non-destructive), and the description goes further with cost (0 credits), plan gating (paid plans only), and the 30-day retention of stopped trackings. Those are non-obvious operational facts an agent cannot get from structured fields.

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?

Front-loaded with the verb and scope, and every clause carries information (returned fields, triggers, retention, cost, plan restriction). It is a single dense run-on block with capitalized emphasis rather than cleanly separated sections, which slightly hurts scanability.

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?

With 6 optional parameters, no output schema, and a dual-mode events_for parameter, the description supplies the return shape, the retention window, the cost, and the follow-up delete path. An agent has everything needed to call it correctly and to interpret the result.

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%, including the mode-switching events_for parameter and both enums, so the schema carries parameter meaning. The description adds no filter syntax or usage nuance beyond listing returned fields, which is the expected baseline-3 case.

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?

Specific verb (LIST) plus resource (the products this API key tracks), and it names the paired sibling track_product so the agent can distinguish creation from enumeration. It also enumerates the returned fields, which matters because there is no output schema.

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?

Explicit 'USE WHEN' triggers cover the main intents: what is tracked, whether a tracking is live, remaining allowance, and stopping one (with the DELETE /v1/track/{id} handoff). It lacks an explicit 'use X instead when...' routing against other list-ish siblings, so it falls short of a 5.

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

All Logimu 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