Mencoro

Search tracked queries

search_tracked_queries

Read-onlyIdempotent

Search and paginate the tracked queries (keywords) of a project with their latest rank positions and metrics. Filter by status (active/paused), engines, countries and a free-text search. Sort by one of: queryText, lastSerpPosition, lastMentionPosition, lastShoppingPosition, lastShareOfVoice, lastPositivityIndex, lastMentionCount, lastCheckedAt. limit is 1-100 (default 20). Answers questions like "list my top queries by share of voice" or "find a specific tracked query".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`search`	No
`sortBy`	No		queryText
`status`	No
`engines`	No	allowed values: chatgpt, claude, perplexity, google_ai_overview, google_ai_mode, google_serp, google_shopping
`countries`	No	ISO-3166 alpha-2 country codes (e.g. "US", "GB", "DE"); a project's configured codes are listed by get_available_filters
`projectId`	Yes
`sortOrder`	No		desc
`organizationId`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / engines / description

Previous value: -"allowed values: chatgpt, perplexity, google_ai_overview, google_ai_mode, google_serp, google_shopping"New value: +"allowed values: chatgpt, claude, perplexity, google_ai_overview, google_ai_mode, google_serp, google_shopping"

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"
+]

Changed24 schema fields changedSep 17, 2026
- addedInput schema / properties / search / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / search / type
```
Removed value: -[
-  "null",
-  "string"
-]
```
- addedInput schema / properties / status / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / status / type
```
Removed value: -[
-  "null",
-  "string"
-]
```
- addedOutput schema / properties / items / items / properties / lastCheckedAt / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastCheckedAt / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / lastLinkPosition / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastLinkPosition / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / lastMentionPosition / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastMentionPosition / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / lastNegativeMentionCount / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastNegativeMentionCount / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / lastNeutralMentionCount / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastNeutralMentionCount / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / lastPositiveMentionCount / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastPositiveMentionCount / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / lastPositivityIndex / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastPositivityIndex / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / lastSerpPosition / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastSerpPosition / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / lastShareOfVoice / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastShareOfVoice / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / lastShoppingPosition / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / lastShoppingPosition / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
First observedSep 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds behavioral context beyond that: it is paginated, supports sorting, and documents the limit bound (1-100, default 20). It does not cover offset behavior or rate limits, keeping it below 5.

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?

Three front-loaded sentences that lead with purpose then capabilities, with no redundant filler. The long sort-field enumeration is dense but earns its place by covering an unlabeled enum.

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?

An output schema exists, so return values need not be spelled out, and the description still hints at returned data (positions and metrics). For a 10-parameter tool it covers most needed guidance, leaving only offset/sortOrder semantics 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 description coverage is only 20%, so the description must compensate and largely does: it names the status values (active/paused), the engines/countries/search filters, the full sortBy field list, and the limit range/default. It omits meaning for offset, sortOrder, and the required org/project IDs.

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 (search) plus resource (tracked queries/keywords) and scope (a project's queries with latest rank positions and metrics). This clearly distinguishes it from get_tracked_query (single) and get_tracked_query_matches (a different resource).

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?

Gives concrete context via example questions ('list my top queries by share of voice', 'find a specific tracked query') and enumerates the filtering dimensions. It implies when to reach for this vs a single-query lookup, but does not explicitly state exclusions or name a sibling alternative.

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.