Skip to main content
Glama
Sign In
surveymonkey-mcp

surveymonkey-mcp

by dscovr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

surveymonkey_delete_contact_list

Delete a SurveyMonkey contact list by providing its list ID. Permanently removes the list and its contacts from your account.

Instructions

Deletes a contact list.

Args: list_id: Contact list ID.

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": {
      "list_id": "<list_id>"
    },
    "name": "surveymonkey_delete_contact_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the operation deletes a contact list, without mentioning consequences such as whether contacts within the list are also removed, irreversibility, permissions, or other side effects.

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?

The description is very short, front-loads the action, and documents the only parameter. It is appropriately concise for a one-parameter tool, though it offers very little beyond the bare minimum.

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

Completeness3/5

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

The tool is simple with one required parameter and an output schema is present, so return values are covered. However, as a destructive operation it omits side-effect and prerequisite context, making completeness only adequate.

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 0%, so the description must compensate. It provides 'list_id: Contact list ID.', which clarifies the parameter slightly beyond the schema's 'List Id', but for a single string ID this adds only minimal semantic value.

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?

The description states a specific verb ('Deletes') and resource ('a contact list'), making it clear that this tool is for deleting contact lists. It does not explicitly contrast with sibling delete tools, but the resource is unambiguous.

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 is provided on when to use this tool versus alternatives. Sibling tools include delete_contact, delete_survey, delete_collector, and delete_contact_list, but the description offers no selection cues or exclusions.

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