mcp

export_form_responses

Read-onlyIdempotent

Export all responses as CSV text or JSON (up to 2,000 rows here; use the web app for larger exports and Excel). Requires the "forms" scope.

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": {
      "form_id": "<form_id>"
    },
    "name": "export_form_responses"
  }
}

Input Schema

Name	Required	Description
`format`	No
`api_key`	No	Your Datronis personal access token (starts with "dtk_"). Generate one at /app/api-keys/. Required unless sent as an `Authorization: Bearer <token>` HTTP header instead (preferred — see search_jobs' api_key description for why).
`form_id`	Yes	Form id — from list_forms or create_form.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes beyond the annotations (which already declare read-only, idempotent, non-destructive, closed-world) by disclosing the hard 2,000-row ceiling, the redirect to the web app for bigger data, and the required "forms" scope. It could add whether exports are synchronous or whether all matching responses are always included, but the operational constraints given are genuinely useful.

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 tight sentence with the capability front-loaded, the row limit and workaround in a parenthetical, and the auth requirement last. Nothing is redundant.

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 read-only export with no output schema, the description covers format, scale limit, fallback path, and required scope — enough to invoke correctly. Only the format default and whether the export is truncated versus rejected at the limit are unstated.

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?

Schema coverage is 67% and the format enum has no schema description, so the description's mapping of csv/json to 'CSV text or JSON' does real work. It does not state the default format or how the 2,000-row cap interacts with format choice, but adds clear meaning over the bare enum.

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?

States a specific verb and resource ('Export all responses') plus the output formats (CSV text or JSON), so the agent knows exactly what comes back. It does not explicitly distinguish itself from the nearby list_form_responses or get_form_response siblings, leaving the bulk-vs-paginated distinction implicit.

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

Usage Guidelines4/5

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

Gives a clear when-not rule: larger exports and Excel belong in the web app, with the 2,000-row cutoff stated inline. It stops short of naming list_form_responses as the alternative for browsing individual or paginated responses.

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

All mcp tools Inspect

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

Need Help?