Content Sweep

create_quote

Create a free quote binding one action, complete input, rate version and maximum USD-cent price for 15 minutes. Does not reserve or spend credits and does not grant rights. Returns a quote ID for the matching task tool: search/find_copies, investigate/investigate_url, evidence/capture_evidence, prepare/prepare_takedown, submit/submit_takedown, status/check_status or monitor/monitor_case. Authenticate and include the exact rights-holder, work and delegation scope.

Input Schema

Name	Required	Description	Default
`input`	Yes	Complete input bound into the quote. Every action needs rights_holder_id, work_id and delegation_id. search: main_handle; investigate: url; evidence/status: case_id; prepare: case_id, evidence_id, good_faith, accurate_and_authorized, infringement_explanation; submit: case_id, packet_id; monitor: target_action, expires_at, per_run_limit_cents, total_limit_cents plus main_handle (search) or case_id (status).
`action`	Yes	Billable action whose input and maximum price are bound into this quote.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 8, 2026

addedInput schema / properties / action / description

Added value: +"Billable action whose input and maximum price are bound into this quote."

changedInput schema / properties / input / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / input / description

Added value: +"Complete input bound into the quote. Every action needs rights_holder_id, work_id and delegation_id. search: main_handle; investigate: url; evidence/status: case_id; prepare: case_id, evidence_id, good_faith, accurate_and_authorized, infringement_explanation; submit: case_id, packet_id; monitor: target_action, expires_at, per_run_limit_cents, total_limit_cents plus main_handle (search) or case_id (status)."

addedInput schema / properties / input / properties

Added value: +{
+  "accurate_and_authorized": {
+    "description": "For prepare: true attests the claim is accurate and the signer is authorized.",
+    "type": "boolean"
+  },
+  "cadence_hours": {
+    "default": 24,
+    "description": "For monitor: hours between runs; daily by default.",
+    "maximum": 168,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "case_id": {
+    "description": "Case ID returned by investigate_url, required for evidence, prepare, submit, status and status monitoring.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  },
+  "delegation_id": {
+    "description": "Unrevoked, unexpired delegation ID covering this work and action; submission requires appointment permission.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  },
+  "destination": {
+    "description": "Optional prepare destination from the case's supported enforcement routes; arbitrary recipients are not supported.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  },
+  "evidence_id": {
+    "description": "For prepare: evidence ID for this case with a current observation that the URL is live.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  },
+  "expires_at": {
+    "description": "For monitor: future ISO 8601 expiry, at most 366 days away.",
+    "format": "date-time",
+    "type": "string"
+  },
+  "good_faith": {
+    "description": "For prepare: true attests a good-faith belief the use is unauthorized.",
+    "type": "boolean"
+  },
+  "infringement_explanation": {
+    "description": "For prepare: rights holder's factual explanation of the suspected infringement; stored as a customer assertion.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  },
+  "main_handle": {
+    "description": "For search, or monitor targeting search: creator identity/handle used for existing text and identity queries.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  },
+  "packet_id": {
+    "description": "For submit: ready packet ID returned by prepare_takedown for this case and delegation.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  },
+  "per_run_limit_cents": {
+    "description": "For monitor: maximum USD cents reserved for one recurring run.",
+    "maximum": 100000,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "rights_holder_id": {
+    "description": "Rights-holder ID returned by create_rights_holder in this organization.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  },
+  "scenario": {
+    "description": "Sandbox status fixture only: simulate a missing page. Repeated timestamped observations are still required to conclude removal.",
+    "enum": [
+      "removed"
+    ]
+  },
+  "target_action": {
+    "description": "For monitor: recurring discovery (search) or fresh observations of an existing case (status).",
+    "enum": [
+      "search",
+      "status"
+    ]
+  },
+  "total_limit_cents": {
+    "description": "For monitor: lifetime recurring-run budget in USD cents, at least the per-run limit.",
+    "maximum": 100000,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "url": {
+    "description": "For investigate: suspected-copy public HTTP(S) URL. Private network targets are refused.",
+    "format": "uri",
+    "type": "string"
+  },
+  "work_id": {
+    "description": "Work ID returned by create_work for this rights holder.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  }
+}

addedInput schema / properties / input / required

Added value: +[
+  "rights_holder_id",
+  "work_id",
+  "delegation_id"
+]

First observedSep 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover the safety profile (non-destructive but not read-only, non-idempotent, open-world), and the description adds genuinely new behavioral context: a 15-minute validity window, no credit reservation, no rights granted, and an authentication/delegation-scope requirement. It also discloses the exact prerequisites (rights-holder, work, delegation scope) needed to call it.

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 sentences, front-loaded with the core semantics and TTL before the routing and auth details. The enumerated sibling list is long but each entry is load-bearing for selecting the follow-up tool; no filler sentences.

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?

With no output schema, the description correctly states what is returned (a quote ID) and how to consume it. It covers expiry, cost semantics, auth requirements, and downstream routing, so an agent has everything needed despite the tool's nested, multi-action complexity.

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% and the nested input schema already documents every action-to-field mapping in detail. The description reinforces "complete input" and the per-action binding but adds no field-level meaning beyond the schema, so the baseline 3 applies.

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 ("Create a free quote") plus the exact scope it binds (action, complete input, rate version, max USD-cent price, 15-minute TTL). It immediately distinguishes itself from sibling task tools by naming what it does not do (reserve/spend credits, grant rights).

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 routes the agent: the returned quote ID feeds one of seven named sibling tools (find_copies, investigate_url, capture_evidence, prepare_takedown, submit_takedown, check_status, monitor_case), and it clearly excludes reservation/spending. When-to-use and what-it-is-not are both stated.

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

All Content Sweep 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?