Skip to main content
Glama
SurfRankAI

SurfRank MCP Server

by SurfRankAI

delete_project

Delete a project and all its keywords, reports, and analyses permanently.

Instructions

Permanently delete a project and all of its keywords, reports, and analyses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes

Implementation Reference

  • The handler function that executes the delete_project logic by making a DELETE API call to /projects/{projectId}
    handler: async ({ projectId }) => api.delete(`/projects/${projectId}`),
  • Input schema for delete_project: requires a single string parameter 'projectId'
    inputSchema: {
      type: 'object',
      properties: { projectId: { type: 'string' } },
      required: ['projectId'],
    },
  • Tool registration within the projectTools array, exported and then spread into ALL_TOOLS in src/index.js
    {
      name: 'delete_project',
      description: 'Permanently delete a project and all of its keywords, reports, and analyses.',
      inputSchema: {
        type: 'object',
        properties: { projectId: { type: 'string' } },
        required: ['projectId'],
      },
      handler: async ({ projectId }) => api.delete(`/projects/${projectId}`),
    },
  • src/index.js:31-39 (registration)
    Central registration: projectTools (including delete_project) are spread into the ALL_TOOLS array and mapped by name for dispatch
    const ALL_TOOLS = [
      ...projectTools,
      ...keywordTools,
      ...reportTools,
      ...quickTestTools,
      ...keywordResearchTools,
      ...competitorTools,
      ...opportunityTools,
    ];
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions 'permanently delete' but does not elaborate on side effects, permissions required, reversibility, or consequences beyond the listed items.

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 a single sentence with no wasted words, but it could be improved by more explicitly front-loading the action. Still, it is concise enough.

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

Completeness2/5

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

Given the tool is destructive (no annotations, no output schema), the description should provide more context such as confirmation of deletion, error conditions, or cascading effects. The current text is minimal and leaves important gaps.

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

Parameters1/5

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

The single parameter 'projectId' has no description in the schema (0% coverage), and the description does not add any context about its format, source, or purpose. The agent receives no help understanding how to provide this 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?

The description clearly states the action (permanently delete) and the resource (project), and explicitly specifies the scope by naming associated items (keywords, reports, analyses). This distinguishes it from sibling tools like delete_competitor or delete_keyword.

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 (e.g., other delete tools) or any prerequisites. The description lacks explicit context for usage decisions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SurfRankAI/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server