Skip to main content
Glama
Sign In
tokportal-mcp

tokportal-mcp

Official
by tokportal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tokportal_list_bundle_videos

Read-onlyIdempotent

Retrieve video slots in a bundle to inspect available positions for scheduling social media content.

Instructions

List bundle video slots.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesBundle ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no extra behavioral context (e.g., pagination, ordering, or what 'slots' means), but with annotations present this is acceptable. No contradiction with 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?

The description is a single, concise sentence with no filler. It front-loads the action and resource clearly, making it maximally efficient.

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 one-parameter list operation with annotations, the description is mostly adequate. However, the tool name says 'videos' while the description says 'slots', which could confuse agents about what exactly is returned. No output schema or additional context is provided, so completeness is slightly compromised.

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 coverage is 100% with a single parameter 'id' described as 'Bundle ID', which is clear. The tool description itself does not add meaning beyond the schema, but the schema does the heavy lifting, so a baseline 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 'List bundle video slots' uses a specific verb and resource, clearly distinguishing it from sibling tools like 'tokportal_get_bundle_video' (retrieves a single video) and 'tokportal_list_bundles' (lists bundles). The action is unambiguous and actionable.

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?

The description provides no guidance on when to use this tool compared to alternatives. It does not mention any exclusions, prerequisites, or related tools, leaving the agent to infer usage solely from the name.

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