Skip to main content
Glama

List surveys

surveys_list
Read-onlyIdempotent

Lists the workspace’s surveys with status (draft, open or closed), response count, questions (with ids and whether each can be answered from an email) and, when open, the public link to share. Free and read only. Use survey_results for the answers. Requires API key scope: read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "surveys_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds context those annotations do not carry: the operation is free, it requires the 'read' API key scope, and the public link is only present for open surveys, which prevents an agent from treating a missing link as an error.

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?

It is front-loaded: the content of the listing comes first, then cost/safety, then the sibling route, then the auth requirement. The only minor redundancy is 'read only,' which restates readOnlyHint=true, but 'Free' and the scope requirement are novel and earn their space.

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?

With no output schema, the description carries the full burden of describing return values and does so field by field, including the conditional public link. Combined with the explicit API key scope and the pointer to survey_results, an agent has everything needed to call this correctly.

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?

There are zero input parameters, so parameter semantics hit the baseline of 4. The description correctly spends its effort on return-shape semantics instead of inventing filter arguments that do not exist.

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?

The description opens with a specific verb and resource ('Lists the workspace's surveys') and then enumerates exactly what each entry contains: status values, response count, question ids, and the public link. It also separates itself from the sibling that returns answers, so an agent can distinguish surveys_list from survey_results on the description alone.

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?

It gives one explicit routing rule: 'Use survey_results for the answers,' which tells the agent which sibling to pick when the goal is response data rather than survey metadata. It does not spell out exclusions for the other list siblings (campaigns_list, segments_list), but the survey scope makes the boundary clear enough in practice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources