Skip to main content
Glama

Video Transcript MCP for TikTok, Instagram Reels & YouTube — Mira

Mira account

get_account
Read-only

Show the Mira plan, today's usage and a link to manage or cancel the subscription.

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": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes the safety profile, so the description's contribution is the useful disclosure that cancellation is not performed here but surfaced as a link to an external management page. That distinguishes reading from acting and prevents an agent from expecting this tool to mutate the subscription. It stops short of noting auth requirements or how stale "today's usage" may be.

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 sentence with no filler, front-loading the resource (Mira plan) followed by the concrete payload items. Every clause earns its place by naming a returned field or the out-of-band action link.

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 parameters, readOnly annotations and no output schema, the description carries the burden of describing return contents and does so by listing plan, usage, and management link. The main residual gap is that it does not state what happens when no subscription exists or whether authentication is required.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to explain. The description appropriately spends its words on return contents rather than inventing input details.

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

Purpose4/5

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

"Show the Mira plan, today's usage and a link to manage or cancel the subscription" states a concrete verb (show) and enumerates the exact resource contents the agent will receive. An agent can tell this is an account/billing-info read, but the description does not distinguish it from sibling tools such as get_result, relying instead on the name alone for that separation.

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?

Usage is only implied: an agent infers it should call this when a user asks about their plan, usage, or subscription. There is no explicit when-to-use statement, no mention of preconditions (e.g. authentication required) and no named alternative, though the sibling set (get_result, parse_video) appears unrelated, so the omission is low-risk.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.