Skip to main content
Glama

Revdoku

by com.revdoku
OverviewDiscussionsAdmin

Bucket Publication List

bucket_publication_list
Read-onlyIdempotent

List active and historical bucket website publications visible to this MCP connector.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucket_idNoRevdoku bucket id returned by bucket_list or bucket_get, for example bkt_...
account_idNoOptional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a bucket id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
publicationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Optional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a bucket id.",
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable scope details: it lists both active and historical publications and limits the result set to those visible to this MCP connector, which clarifies expected behavior beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, focused sentence with no filler or redundancy. Key qualifiers ('active and historical', 'visible to this MCP connector') are front-loaded and directly support the agent's decision-making.

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?

For a simple read-only listing tool with full schema coverage and output schema available, the description covers the essential scope. It might be strengthened by naming sibling tools like bucket_publication_get, but the omission does not block correct use.

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 both bucket_id and account_id are already documented with meaningful context. The description adds no parameter-specific guidance, but the schema fully covers parameter semantics, so the baseline score of 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?

The description states a specific action ('List'), a specific resource ('bucket website publications'), and a clear scope ('active and historical', 'visible to this MCP connector'). It clearly identifies what the tool does and distinguishes it from retrieval tools like bucket_publication_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives enough context to infer when to use it—when you want to enumerate publications visible to the connector—but it does not explicitly contrast it with sibling tools such as bucket_publication_get or mention any preconditions, exclusions, or alternative selection guidance.

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

All Revdoku 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