Skip to main content
Glama

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

NameRequiredDescriptionDefault
limitNo
offsetNo
searchNo
sortByNoqueryText
statusNo
enginesNoallowed values: chatgpt, claude, perplexity, google_ai_overview, google_ai_mode, google_serp, google_shopping
countriesNoISO-3166 alpha-2 country codes (e.g. "US", "GB", "DE"); a project's configured codes are listed by get_available_filters
projectIdYes
sortOrderNodesc
organizationIdYes

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / items / items / properties / lastHadLink
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. Changed4 schema fields changed
    • addedOutput schema / properties / items / items / properties / lastHadAppearance
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / items / items / properties / lastHadMention
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / items / items / properties / lastHadSerpResult
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / items / items / properties / lastHadShoppingResult
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  3. Changed2 schema fields changed
    • 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"
      +]
  4. Changed24 schema fields changed
    • 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"
      -]
  5. First observed

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/openWorld=false, so safety is covered; the description adds genuinely new behavior: pagination via limit/offset, a 1-100 limit range with default 20, and that results carry latest rank positions and metrics. It omits rate limits or scope/permission expectations, but adds solid context beyond the 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?

Four dense sentences, front-loaded with the core action before the filter/sort details and the example questions. The sort enum listing is long but functional; nothing reads as filler.

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 explained, and the description supplies the filtering, sorting, pagination and use-case context an agent needs to call a 10-parameter read tool correctly. Minor gaps remain around offset/sortOrder semantics and id-parameter provenance (organizationId/projectId).

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?

With only 20% schema coverage, the description carries most of the burden and does so: it names the filterable params (status active/paused, engines, countries, free-text search), reproduces the full sortBy enum, and states the limit range and default. It leaves offset, sortOrder and the id params to the schema, so it is strong but not exhaustive.

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+resource ('Search and paginate the tracked queries (keywords) of a project') with the returned payload ('latest rank positions and metrics'), which cleanly separates it from the singular get_tracked_query and the mutation siblings like create/delete/pause_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 Guidelines4/5

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

Gives concrete use cases ('list my top queries by share of voice', 'find a specific tracked query') and enumerates the filterable facets, so an agent knows when this tool applies. It does not explicitly exclude or route to a sibling (e.g. get_tracked_query for a single query by id), so it stops 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.