API Monitor MCP

Overview Schema Source Related Servers Discussions Admin

capture_export_calls

Export a bounded page of saved API calls to JSON or CSV. Use it to save or share specific call records from a capture file, with control over range, format, and data size.

Instructions

Export a bounded saved call-record page as JSON or CSV.

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": {
      "file_path": "<file_path>",
      "output_path": "<output_path>"
    },
    "name": "capture_export_calls"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`file_path`	Yes
`overwrite`	No
`output_path`	Yes
`start_index`	No
`include_data`	No
`output_format`	No	json
`process_index`	No
`max_data_bytes`	No
`resolve_definitions`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.26Sep 12, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden and mostly does not: it never says overwrite semantics, whether an existing output_path errors, what permissions/locks are needed, or whether the export is destructive. 'bounded' and the format list are the only behavioral hints.

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?

A single front-loaded sentence with no filler, which is good structurally. However, its brevity here reflects under-specification rather than economy, so it is adequate but not exemplary.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter export tool with no annotations and zero schema descriptions, the description is far from complete, though the presence of an output schema excuses it from explaining the return shape. Required inputs (file_path, output_path) and mutation risks go unexplained.

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 coverage is 0% and there are 10 parameters. The description only implies output_format (JSON/CSV) and paging via limit/start_index; it says nothing about file_path, output_path, overwrite, include_data, max_data_bytes, resolve_definitions, or process_index, leaving most parameters undocumented anywhere.

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?

The sentence names a specific verb (Export) and resource (saved call-record page) and notes the two output formats, so an agent knows what it does. It does not distinguish the tool from near-siblings like capture_extract_call_payload or capture_call_records, so it falls short of a 5.

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 statement of when to use this over the many other capture tools, and no prerequisites (e.g. that a capture must already be saved/loaded). 'bounded page' hints at incremental export but does not route the agent.

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

Deploy Server