Skip to main content
Glama

Opedd — Licensed Content for AI

by com.opedd
OverviewDiscussionsAdmin

list_publisher_content

List all licensable articles for the authenticated publisher (requires OPEDD_PUB_BEARER, or legacy OPEDD_API_KEY). Returns articles with titles, descriptions, pricing, and sales statistics. Set include_body=true to read back the STORED article text exactly as licensed buyers receive it (this is how you check that a push_content call stored what you meant; bodies are truncated to 8,000 characters per article, page size 20, paginate with cursor). Use article IDs from this list to purchase licenses via purchase_license.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoWith include_body=true: fetch exactly one of your articles by id (full body, no truncation).
typeNoFilter by license type availability (ignored when include_body is true)
limitNoNumber of results (default: 20, max: 100; max 20 when include_body is true)
cursorNoOpaque next_cursor from a previous include_body=true call.
offsetNoPagination offset (default: 0; ignored when include_body is true — use cursor)
include_bodyNoReturn each article's stored body (what buyers receive). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque next_cursor from a previous include_body=true call.",
+  "type": "string"
+}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "With include_body=true: fetch exactly one of your articles by id (full body, no truncation).",
+  "type": "string"
+}
    • addedInput schema / properties / include_body
      Added value: +{
+  "description": "Return each article's stored body (what buyers receive). Default false.",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results (default: 20, max: 100)"New value: +"Number of results (default: 20, max: 100; max 20 when include_body is true)"
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset (default: 0)"New value: +"Pagination offset (default: 0; ignored when include_body is true — use cursor)"
    • changedInput schema / properties / type / description
      Previous value: -"Filter by license type availability"New value: +"Filter by license type availability (ignored when include_body is true)"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly: it discloses authentication requirements, the exact stored-body readback semantics, 8,000-character truncation, page size 20, cursor pagination, and the push_content verification workflow. This goes well beyond the structured schema.

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, each earning its place: scope/auth, returned fields, include_body semantics with truncation and pagination, and the downstream license-purchase workflow. The long parenthetical sentence is information-dense rather than filler, though it is slightly heavy.

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?

Given the absence of annotations and output schema, the description is quite complete: it covers auth, return fields, pagination, truncation, and a practical verification workflow. It does not detail error behavior or the exact response envelope beyond article fields, but the combination of description and schema is sufficient for correct invocation.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful context to include_body (stored text exactly as buyers receive it, truncation, verification of push_content) and pagination via cursor. It does not substantially enrich id/type/limit/offset, but those are already well documented in 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?

The description opens with a specific verb, resource, and scope: 'List all licensable articles for the authenticated publisher.' It further differentiates the tool by naming its downstream role ('Use article IDs from this list to purchase licenses via purchase_license'), which distinguishes it from generic content get/search/lookup siblings.

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?

The description provides clear context for when to use this tool: listing the publisher's licensable articles, verifying what push_content stored via include_body=true, and obtaining IDs for purchase_license. It does not explicitly state when not to use it or name alternative listing tools, 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.

All Opedd — Licensed Content for AI toolsInspect
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