Content Sweep

create_rights_holder

Register a rights holder managed by this organization, without a creator login or subscription. Requires rights scope. Supply a person/business name and optional country/contact email; returns a rights-holder id for create_work and delegate_authority. Registration records identity and does not itself authorize enforcement.

Input Schema

Name	Required	Description	Default
`body`	Yes	Rights-holder name (required), optional two-letter country_code and contact_email. Use the returned id as rights_holder_id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 8, 2026

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

addedInput schema / properties / body / description

Added value: +"Rights-holder name (required), optional two-letter country_code and contact_email. Use the returned id as rights_holder_id."

addedInput schema / properties / body / properties

Added value: +{
+  "contact_email": {
+    "format": "email",
+    "type": "string"
+  },
+  "country_code": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "name": {
+    "minLength": 1,
+    "type": "string"
+  }
+}

addedInput schema / properties / body / required
```
Added value: +[
+  "name"
+]
```

First observedSep 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations cover the safety profile (mutation, non-idempotent, non-destructive, open world). The description adds real value beyond them: the rights-scope prerequisite, that the caller needs no creator login or subscription, and crucially that registration records identity but does not authorize enforcement.

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?

Two tight sentences, front-loaded with the core action and constraint before the id/return detail. No filler, though the clause list is slightly dense.

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?

With no output schema, the description correctly supplies the return value (a rights-holder id) and its downstream use. Prerequisites and the enforcement caveat are present; only a pagination/error-shape note is absent, which is minor for a create tool.

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 schema itself documents name (required), country_code, and contact_email plus the "Use the returned id as rights_holder_id" note. The description restates name/country/email without adding format or constraint detail 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 (Register) and resource (rights holder) scoped to "managed by this organization," and clarifies it happens without a creator login or subscription. This cleanly separates it from siblings like create_work and delegate_authority.

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?

It names the context (registering a managed holder without creator login/subscription), states the prerequisite (requires rights scope), and points at the downstream tools that consume the id (create_work, delegate_authority). No explicit when-not-to-use beyond the enforcement disclaimer.

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?