formset

Export responses

export_responses

Read-only

Get a download link for every response to a form, as a spreadsheet (CSV, which opens directly in Excel, Numbers and Google Sheets) or as JSON. Use this when someone wants the whole dataset in their own hands — "send me the responses", "export this", "can I get a spreadsheet".

Returns a link, not the data: a few thousand answers do not belong in a conversation. For questions you can answer here — counts, totals, which option is winning — use get_response_stats, and for reading particular answers use list_responses.

The link works for one hour and needs no login, so treat it as sensitive and give it only to the person who asked.

Example: { form_id: "…", format: "csv" }

Input Schema

Name	Required	Description	Default
`format`	No	csv (default) or json.
`form_id`	Yes	The form id from create_form or list_forms, or the slug from its share link (the part after /f/).

Output Schema

Name	Required	Description	Default
`url`	No
`format`	No
`refused`	No
`expires_at`	No
`response_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

addedOutput schema / properties / refused

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "reason",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "url",
-  "format",
-  "expires_at",
-  "response_count"
-]

Changed4 schema fields changedOct 17, 2026

addedOutput schema / additionalProperties
```
Added value: +false
```

removedOutput schema / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "expires_at": {
-        "type": "string"
-      },
-      "format": {
-        "type": "string"
-      },
-      "response_count": {
-        "type": "number"
-      },
-      "url": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "format",
-      "expires_at",
-      "response_count"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "refused": {
-        "additionalProperties": false,
-        "properties": {
-          "message": {
-            "type": "string"
-          },
-          "reason": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "reason",
-          "message"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "refused"
-    ],
-    "type": "object"
-  }
-]

addedOutput schema / properties

Added value: +{
+  "expires_at": {
+    "type": "string"
+  },
+  "format": {
+    "type": "string"
+  },
+  "response_count": {
+    "type": "number"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "url",
+  "format",
+  "expires_at",
+  "response_count"
+]

Changed4 schema fields changedOct 17, 2026

removedOutput schema / additionalProperties
```
Removed value: -false
```

addedOutput schema / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "expires_at": {
+        "type": "string"
+      },
+      "format": {
+        "type": "string"
+      },
+      "response_count": {
+        "type": "number"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "url",
+      "format",
+      "expires_at",
+      "response_count"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "refused": {
+        "additionalProperties": false,
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "reason": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "reason",
+          "message"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "refused"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "expires_at": {
-    "type": "string"
-  },
-  "format": {
-    "type": "string"
-  },
-  "response_count": {
-    "type": "number"
-  },
-  "url": {
-    "type": "string"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "url",
-  "format",
-  "expires_at",
-  "response_count"
-]

First observedOct 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive), and the description adds the traits that actually matter: it returns a link and not the data, the link expires in one hour, it needs no login, and it should be treated as sensitive and shared only with the requester.

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?

Front-loads what the tool returns, then usage triggers, then alternatives, then the expiry security note. Every sentence carries distinct information; none is padding or restatement of the name.

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

Completeness5/5

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

Output schema exists, so return values need no prose, and the description still clarifies the critical shape (a link, not the data) plus its lifetime. An agent has everything needed to call this correctly and to warn about link sensitivity.

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 the baseline is 3, but the description adds value beyond it by explaining what format means in practice (CSV opens directly in Excel, Numbers, Google Sheets) and by showing a concrete example call with form_id and format.

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?

States a specific verb (get a download link) and resource (every response to a form) plus the output formats (CSV or JSON). It explicitly distinguishes itself from get_response_stats and list_responses, so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use triggers ("send me the responses", "export this", "can I get a spreadsheet") and names two alternatives with the conditions that select them: get_response_stats for counts/totals, list_responses for particular answers. Nothing is left to inference.

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

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