Organiq GEO

Indexing requests

get_indexing_requests

Read-onlyIdempotent

Lists the indexing requests made for the property (from request_indexing, the panel or the sitemap job), newest first: url, engine (indexnow / google), action, source (manual / sitemap / agent), status (queued, submitted, failed, skipped), queuedAt, submittedAt, httpStatus and error (the cause of a failed or skipped request; starts with google_not_eligible when the page has no JobPosting or BroadcastEvent structured data). Filter by status; days = how far back (default 7, max 365). Returns counts per status and per engine, plus the daily credit per route (indexnow and google: used, limit, left; null = no limit). Reads only Organiq data. A sent request is not a confirmation; the confirmed state comes from the inspection (get_indexing_tracker). Use after request_indexing to see what was sent or why a request failed. / Pedidos de indexação da propriedade, com status por motor e crédito do dia.

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": {
      "site": "<site>"
    },
    "name": "get_indexing_requests"
  }
}

Input Schema

Name	Required	Description
`days`	No	Days back (default 7).
`site`	Yes	Property: displayName ("example.com"), Search Console siteUrl ("sc-domain:example.com", "https://www.example.com/") or numeric id. A unique substring among visible properties also works ("exam"). list_sites shows the options. The value "demo" selects a demonstration site with fictional data: it works without signing in and is read-only. / Propriedade por nome, siteUrl ou id; "demo" é um site de demonstração com dados fictícios, sem login e só leitura.
`limit`	No	Rows (default 100).
`status`	No	Only requests with this status.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / site / description

Previous value: -"Property: displayName (\"example.com\"), Search Console siteUrl (\"sc-domain:example.com\", \"https://www.example.com/\") or numeric id. A unique substring among visible properties also works (\"exam\"). list_sites shows the options. / Propriedade por nome, siteUrl ou id."New value: +"Property: displayName (\"example.com\"), Search Console siteUrl (\"sc-domain:example.com\", \"https://www.example.com/\") or numeric id. A unique substring among visible properties also works (\"exam\"). list_sites shows the options. The value \"demo\" selects a demonstration site with fictional data: it works without signing in and is read-only. / Propriedade por nome, siteUrl ou id; \"demo\" é um site de demonstração com dados fictícios, sem login e só leitura."

AddedOct 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotent annotations, the description discloses output fields, status and engine breakdowns, daily credit limits, error-cause semantics, and the crucial caveat that a sent request is not a confirmed indexing state. It also scopes the data source to Organiq only.

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?

The description is dense but front-loaded: purpose and returned fields come first, then filtering, then the sent-vs-confirmed caveat and usage guidance. The bilingual repetition adds length, but no sentence is clearly wasted.

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?

There is no output schema, so the description carries the return-value burden and does so thoroughly: it lists fields, counts per status and engine, and credit-per-route details. Combined with 100% schema coverage for inputs and existing annotations, an agent has enough to call this correctly.

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 the schema already documents site, days, limit, and status. The description restates the days default and maximum and mentions status filtering, but adds little syntax or meaning beyond the schema; baseline 3 is appropriate.

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 and resource ('Lists the indexing requests made for the property'), specifies ordering ('newest first'), and enumerates the returned fields. It clearly distinguishes this read/list tool from request_indexing and get_indexing_tracker.

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?

Explicitly says to use it after request_indexing to see what was sent or why a request failed. It also names the alternative for confirmed state ('the confirmed state comes from the inspection (get_indexing_tracker)'), giving clear when-to-use and when-to-use-another-tool guidance.

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

All Organiq GEO 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.