Skip to main content
Glama
Sign In
Reedapt MCP server

Reedapt MCP server

Official
by Reedapt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List dubs

list_dubs
Read-only

Retrieve your account's dubs newest first with limit and offset pagination to review or manage dubbed audio and video.

Instructions

The account's API dubs, newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_dubs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description contributes the account scoping and the newest-first ordering, which are genuinely beyond the annotations, but it says nothing about pagination behavior, page size limits, or what a returned dub record looks like.

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

Conciseness3/5

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

It is a single short fragment with zero wasted words and the key scoping fact up front. But the brevity comes from under-specification rather than efficiency, so it earns only a middling score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 two conventional parameters and no output schema, the essentials are present and the annotations cover safety. Still, an agent gets no information on result shape, total counts, or the meaning of limit/offset in this API, which are meaningful gaps for a paged list endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both limit and offset, so the description must carry the burden and does not: neither parameter is mentioned, nor is there any hint about default page size or how to page through results. The only related content is the ordering claim, which does not explain the paging parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and its scope ("The account's API dubs") and adds the ordering ("newest first"), so an agent can infer this is a listing operation. However it is an elliptical noun phrase with no explicit verb, and it does not distinguish itself from siblings like get_dub or list_languages beyond the plural/scoping hint.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to prefer this over get_dub for a single record or over list_languages for a different resource. The only contextual signal is the sort order, which does not help an agent choose between tools.

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

Deploy Server

Other Tools