Movahedi Privacy API

List AI crawlers in the registry

list_crawlers

Read-onlyIdempotent

List AI crawlers from the registry, optionally filtered by operator (OpenAI, Anthropic, Google), purpose (training, search-index, user-triggered, search-and-training, other), or status (active, retired, renamed). Use it to compare how operators split training from search agents, or to find every training crawler before writing robots.txt rules. Results are paginated. Use when: Use when someone wants to browse AI crawlers by operator, purpose, or status. Do not use when: Do not use when someone names one exact token; look that token up directly.

Input Schema

Name	Required	Description
`limit`	No	Maximum records to return in this call.
`query`	No	Free-text search over token, operator, and notes.
`offset`	No	Number of matching records to skip. Use next_offset to page forward.
`status`	No	Limit to one lifecycle status.
`purpose`	No	Limit to one purpose class.
`operator`	No	Limit to one operator, matched exactly but case-insensitively, for example 'OpenAI'.

Output Schema

Name	Required	Description
`results`	Yes	Matching crawler records (summary fields; call lookup_crawler for the full record).
`has_more`	Yes	True when more results exist beyond this page.
`truncated`	Yes	True when results were shortened to fit the 50 KB output cap. Use the paginated REST API for the full set.
`next_offset`	Yes	Pass as 'offset' in the next call to continue paging. Null when has_more is false.
`total_count`	Yes	Total number of matches across all pages.
`corpus_version`	Yes	Semantic version of the movahedi.ca statutory corpus this answer was drawn from, for example v2026.12.0. Pin it when citing; when it changes, re-read the affected resources and the change log at https://movahedi.ca/changelog/.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

addedOutput schema / properties / corpus_version

Added value: +{
+  "description": "Semantic version of the movahedi.ca statutory corpus this answer was drawn from, for example v2026.12.0. Pin it when citing; when it changes, re-read the affected resources and the change log at https://movahedi.ca/changelog/.",
+  "examples": [
+    "v2026.12.0"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "results",
-  "total_count",
-  "has_more",
-  "next_offset",
-  "truncated"
-]New value: +[
+  "results",
+  "total_count",
+  "has_more",
+  "next_offset",
+  "truncated",
+  "corpus_version"
+]

AddedOct 24, 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, and closed-world, so the safety burden is largely carried. The description adds real context beyond that: results are paginated, and it enumerates the accepted operator/purpose/status value spaces. It stops short of describing result shape or how next_offset is returned, but with an output schema present that gap is minor.

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?

Well front-loaded: purpose and filters come first, then the exclusion, and every sentence is functional. Minor waste in the 'Use when' line, which restates the opening sentence's browse-by-operator-purpose-status framing almost verbatim.

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?

Six optional params with an output schema and full annotations mean the description doesn't need to explain returns. It covers purpose, filters, pagination, and the sibling alternative; the only real omission is the 'query' free-text search mode, which is a moderately important capability for an agent choosing this tool over lookup_crawler.

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 coverage is 100%, so all six parameters are already documented, and the description's value lists (OpenAI/Anthropic/Google, training/search-index/user-triggered, active/retired/renamed) largely restate the enums. It never mentions the free-text 'query' parameter or limit/offset, so it adds little meaning beyond 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?

States a specific verb and resource ('List AI crawlers from the registry') plus the three filter dimensions, and explicitly distinguishes itself from the token-level sibling by saying not to use it when one exact token is named. An agent can route between list_crawlers and lookup_crawler from the description alone.

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?

Has explicit 'Use when' and 'Do not use when' clauses, with the exclusion naming the concrete alternative behavior ('look that token up directly'). It also gives two motivating scenarios (comparing operator splits, pre-robots.txt audits) that tell an agent when this tool is the right entry point.

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

All Movahedi Privacy API 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.

Resources

Need Help?