Conecto

Export responses to CSV

forms_export_responses

A CSV file of a form's responses in the file store, with a download link: one row per response, oldest first, one column per field in form order, then the link values. Opens in Excel, Numbers and Google Sheets. With since, only responses from then on. Free when there is nothing to export. Costs $0.001 per call; nothing if it fails.

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": "<form>"
    },
    "name": "forms_export_responses"
  }
}

Input Schema

Name	Required	Description
`form`	Yes	The form's form_id or slug (forms_list shows both).
`since`	No	Only responses from this time on: ISO 8601 (2026-10-01T00:00:00Z) or a date (2026-10-01, UTC).
`link_hours`	No	How long the download link works, in hours (up to 168, one week).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the cost model ($0.001 per call, free on empty, refunded on failure) and the output ordering ('oldest first'). It does not explain that each call mints a fresh link (relevant given idempotentHint=false), leaving one meaningful behavior implicit.

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?

Dense and front-loaded: format first, then ordering/layout, then filter, then cost. Every clause carries information; 'Opens in Excel, Numbers and Google Sheets' is the only mildly padded sentence and it still reassures on interoperability.

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 output schema, the description compensates by describing the produced artifact – one row per response, oldest first, one column per field plus link values – and the pricing/failure behavior. What's missing is only the non-idempotent link regeneration nuance.

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 100%, so baseline is 3, but the description adds real value by implying what since does to the result set and describing the resulting row/column layout, which no schema field documents. It doesn't elaborate on link_hours beyond what the schema states.

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 – exports a form's responses as a CSV file with a download link – plus the row/column structure. It never names the obvious alternative (forms_list_responses), so sibling differentiation is only implied by the 'CSV file' framing.

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?

Explains the since filter and the free-when-empty case, which hints at when it makes sense, but gives no explicit guidance on when to prefer this over forms_list_responses or forms_get_response. Usage is inferable rather than stated.

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

All Conecto 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?