# Summarise what respondents said

> Summarise what respondents said: 1 companies fully do it, 9 with a limit, 10 carry the tag. Every listing in Forms, surveys & structured intake with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/forms.summarise-results/
- Markdown: https://www.anchorterminal.com/niches/forms.summarise-results/index.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/niches/forms.summarise-results/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/forms.summarise-results/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 9 | 10 | 5 | 1 |

## What counts as done

A summary with counts per choice and themes from open text, from aggregate endpoints or a full paged read.

Measured, for our own tests: in under a minute.

How agents ask for it: summarise this survey; what are the top complaints; report on this quarter's NPS

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Formbricks (Formbricks GmbH)**: count_responses, dashboards and get_chart_data return aggregated numbers, and every survey has a Summary view, but no time figure is given against the one-minute bar.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Alchemer (Alchemer LLC)**: A surveyreport object exists alongside full paged response reads, but aggregate counts per option weren't confirmed in the pages read.
- **Fillout (Restly, Inc.)**: No aggregate results endpoint; a summary needs a full paged read at up to 150 submissions a page, which carries labels and types.
- **Formstack (Intellistack, LLC)**: GET submissions/count gives totals and a paged read gives the rest, but no per-option results endpoint exists.
- **Google Forms API (Google LLC)**: No aggregate endpoint; a summary needs responses.list, up to 5,000 a page, plus forms.get to label answers.
- **Jotform (Jotform Inc.)**: Report endpoints exist under user and form, but per-option counts weren't shown; a full paged read with labelled answers is the documented route.
- **Paperform (Paperform Pty Ltd)**: No aggregate endpoint; a summary needs a full cursor-paged read at up to 100 a page plus the fields list for labels.
- **SurveyMonkey (SurveyMonkey Inc.)**: Rollup and trend endpoints return counts per survey, page and question in one call, but they need responses_read_detail, which is capped on Basic, and no timing is stated against the one-minute bar.
- **Tally (Tally BV)**: Analytics endpoints return metrics (visits, submissions, completion rate) and per-question drop-off, but not counts per choice; those need a full read of submissions.
- **Typeform (Typeform SL)**: MCP insights-public_aggregate returns counts, averages, sums and NPS for a field or dataset after insights-public_discover. Access is plan-dependent and no timing is stated against the one-minute bar.
- **Wufoo (SurveyMonkey Inc.)**: Reports and their widgets can be read through the API, but per-option counts depend on reports built in the web app; otherwise a full paged read of entries.

## What stops agents finishing

- results endpoints on enterprise plans only

## Around it

Before: forms.read-responses. After: docs.write-report, messaging.post.

## Where this comes from

Weight 5 of 100 in Forms, surveys & structured intake: 1 of 25 accounts (Typeform MCP for reporting); SurveyMonkey and Typeform vendor pages make it a headline job

As data: https://www.anchorterminal.com/api/v1/use-cases/forms.summarise-results.json, or the MCP tool get_use_case with id forms.summarise-results. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
