Mencoro

Create tracked queries

create_tracked_queries

Start tracking queries: every combination of queryTexts x engines x countries (at most 100) becomes a tracked query, checked now and then on checkFrequency with nPasses passes, each check spending budget. Combinations the project already tracks, repeated ones and Google AI Mode in unsupported countries are skipped and reported. Requires a confirmationToken: call preview_operation with tool "create_tracked_queries" and these arguments first, show the returned plan (what is created, what it costs) to the user, and call this tool only after the user explicitly agrees. Pass a fresh requestId and reuse it if you retry.

Input Schema

TableJSON Schema

Name	Required	Description
`locale`	No	Optional two-letter language the engines should answer in
`engines`	Yes
`nPasses`	Yes	Answers captured per check; more than 1 only for AI engines. Each pass counts as one check against your plan; a Claude pass counts as five.
`countries`	Yes	ISO 3166-1 alpha-2 codes, e.g. ["US", "ES"]
`projectId`	Yes
`requestId`	No	Optional idempotency key, 8-255 printable characters. Reuse it only to retry this same call.
`queryTexts`	Yes
`checkFrequency`	Yes
`organizationId`	Yes
`queryClusterIds`	No
`confirmationToken`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`failed`	No	Always present, empty list included: read it rather than inferring success from the status code.
`successful`	No	Tracked queries created by this call, one entry per query text, engine and country combination.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / engines / items / enum

Previous value: -[
-  "chatgpt",
-  "perplexity",
-  "google_ai_overview",
-  "google_ai_mode",
-  "google_serp",
-  "google_shopping"
-]New value: +[
+  "chatgpt",
+  "claude",
+  "perplexity",
+  "google_ai_overview",
+  "google_ai_mode",
+  "google_serp",
+  "google_shopping"
+]

changedInput schema / properties / nPasses / description

Previous value: -"Answers captured per check; more than 1 only for AI engines. Each pass costs one check."New value: +"Answers captured per check; more than 1 only for AI engines. Each pass counts as one check against your plan; a Claude pass counts as five."

AddedSep 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (which only flag write/open-world/non-idempotent), it discloses that checks consume budget, that at most 100 combinations are created, that already-tracked/duplicate/unsupported-country Google AI Mode combinations are skipped and reported, and that a confirmationToken is mandatory. Annotations are not contradicted.

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-loads the core behavior, then the confirmation requirement, then the idempotency note — a logical order with little waste. It is dense but slightly long, and the skipping/cost details are packed into one clause.

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 costly, budget-spending mutation with an output schema present, the description covers the critical operational context: confirmation gating, idempotency, cost, and skip behavior. The gap is a few undocumented parameters (notably queryClusterIds), but no return-value explanation is needed given the output schema.

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 low (36%), and the description compensates well for the core parameters: it explains the combinatorial meaning of queryTexts/engines/countries, the 100-combination cap, and that each check spends budget. However queryClusterIds, locale, and organizationId remain undocumented, and checkFrequency semantics are left to the schema.

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?

Opens with a specific verb+resource ('Start tracking queries') and precisely defines what gets created: the cartesian product queryTexts x engines x countries. It is clearly distinguishable from siblings like update_tracked_queries and delete_tracked_queries.

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?

Gives an explicit precondition workflow: call preview_operation first, show the returned plan/cost to the user, and only call this tool after explicit user agreement. It also states retry guidance for requestId, 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 Mencoro tools Inspect

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.