Skip to main content
Glama
Sign In
surveymonkey-mcp

surveymonkey-mcp

by dscovr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

surveymonkey_delete_survey

Permanently delete a survey and all its responses. This irreversible action removes the survey from your account.

Instructions

Permanently deletes a survey and all its responses. WARNING: irreversible operation.

Args: survey_id: ID of the survey to delete.

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": {
      "survey_id": "<survey_id>"
    },
    "name": "surveymonkey_delete_survey"
  }
}

Input Schema

NameRequiredDescriptionDefault
survey_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/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. It does well by disclosing that deletion is permanent, irreversible, and removes all responses as well as the survey itself. This covers the most important behavioral consequences.

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?

Two tight sentences plus one argument line. The irreversible warning is front-loaded, and there is no filler or repetition. Every sentence earns its place.

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?

For a one-parameter destructive tool, the description covers the target, the cascade to responses, and irreversibility. The output schema exists, so return-value details need not be in the description. It lacks explicit usage/alternative guidance and permission prerequisites, but the essential context is present.

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?

The schema has 0% description coverage and only a bare 'Survey Id' title. The description's 'Args: survey_id: ID of the survey to delete' adds the semantic role of the parameter and confirms it identifies the deletion target. Minimal but sufficient for a single obvious parameter.

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 and resource: 'Permanently deletes a survey and all its responses.' This clearly disambiguates from sibling tools like surveymonkey_delete_response and surveymonkey_delete_collector by naming the target resource and cascade scope.

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?

Provides no guidance on when to choose this tool over the many sibling delete tools, nor any mention of conditions or alternatives. Usage is only implied by the tool name and description, not explicitly stated.

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