Skip to main content
Glama
SurfRankAI

SurfRank MCP Server

by SurfRankAI

delete_competitor

Remove a competitor from a project to keep your competitive analysis focused and up to date.

Instructions

Remove a competitor from a project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes
competitorIdYes

Implementation Reference

  • The handler for 'delete_competitor' that calls the API to delete a competitor. It calls api.delete(`/projects/${projectId}/competitors/${competitorId}`).
      properties: {
        projectId: { type: 'string' },
        competitorId: { type: 'string' },
      },
      required: ['projectId', 'competitorId'],
    },
    handler: async ({ projectId, competitorId }) =>
      api.delete(`/projects/${projectId}/competitors/${competitorId}`),
  • Input schema for 'delete_competitor' defining required parameters: projectId (string) and competitorId (string).
    inputSchema: {
      type: 'object',
      properties: {
        projectId: { type: 'string' },
        competitorId: { type: 'string' },
      },
      required: ['projectId', 'competitorId'],
  • The 'delete_competitor' tool is defined as an object inside the 'competitorTools' array exported from src/tools/competitors.js.
    {
      name: 'delete_competitor',
      description: 'Remove a competitor from a project.',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string' },
          competitorId: { type: 'string' },
        },
        required: ['projectId', 'competitorId'],
      },
      handler: async ({ projectId, competitorId }) =>
        api.delete(`/projects/${projectId}/competitors/${competitorId}`),
    },
  • src/index.js:37-39 (registration)
    The competitorTools array is spread into ALL_TOOLS, which is then registered with the MCP server via ListToolsRequestSchema and CallToolRequestSchema handlers.
      ...competitorTools,
      ...opportunityTools,
    ];
  • The api.delete helper used by the handler. Calls the internal request() function with DELETE method.
    export const api = {
      get: (path, query) => request('GET', path, { query }),
      post: (path, body) => request('POST', path, { body }),
      patch: (path, body) => request('PATCH', path, { body }),
      delete: (path) => request('DELETE', path),
    };
Behavior2/5

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

No annotations provided; description does not disclose side effects, irreversibility, or error conditions beyond the basic action.

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?

Single sentence is concise and front-loaded, no superfluous words.

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?

Adequate for a simple delete operation but lacks information on permanence or validation; no output schema.

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

Parameters2/5

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

Schema description coverage is 0%; description adds no meaning to the required projectId and competitorId parameters.

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?

Clearly states the verb 'remove' and the resources 'competitor from a project', distinguishing it from siblings like add_competitor.

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 on when to use this tool versus alternatives or any prerequisites.

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