Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Forms answers

forms_answers_list
Read-onlyIdempotent

Fetch a form's responses by survey ID. Filter by date, question IDs, and page size; drains pages via cursor to return merged answers.

Instructions

A form's responses, at most limit (drains pages via the next cursor).

Returns the {columns, answers, next} envelope; next is always None in the merged result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax answers to return; omitted means the configured cap (YCLI__HTTP__MAX_ITEMS).
date_toNoISO-8601: answers given at or before.
orderingNo``asc`` is oldest first; the default is ``desc``.
date_fromNoISO-8601: answers given at or after.
page_sizeNoAnswers per request (the API's default is 25).
questionsNoComma-separated question ids to return answers for.
survey_idYesForm id (24-char hex), from ``surveys_list``.
use_slugsNoName questions and options by slug instead of id.
answer_formatNo``default`` (cells aligned to ``columns``) or ``raw`` (each answer's data as stored, with no ``columns``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.122.1
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Max answers to return; omitted means the configured cap (YCLI__HTTP__MAX_ITEMS)."
+}
    • addedInput schema / properties / use_slugs / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / use_slugs / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / use_slugs / type
      Removed value: -"boolean"
  2. First observedv0.67.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds a genuinely useful non-obvious behavior: it drains pages internally via the cursor and merges results so that 'next' is always None in the returned envelope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no waste, and the core behavior (bounded result plus auto-paging) is front-loaded. Minor awkwardness in phrasing ('A form's responses, at most limit') but structurally sound.

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 usefully explains the {columns, answers, next} return envelope and the merged-pagination semantics. Permissions, rate limits, and error behavior are unaddressed, but for a read-only list tool this is largely sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 9 parameters (limit, date_from/to, ordering, page_size, questions, survey_id, use_slugs, answer_format) are already documented in the schema. The description only adds meaning for 'limit' and the envelope shape, so the baseline 3 applies.

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+resource: listing a form's responses/answers, and clarifies the paging model. It does not explicitly differentiate from siblings like forms_answers_get or forms_answers_export, so an agent must infer the distinction from the name.

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?

No guidance on when to choose this over forms_answers_get, forms_answers_export, or forms_answers_integrations_list, and no prerequisites or exclusions are stated. Usage is only implied by the verb 'list'.

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

Deploy Server

Other Tools