Skip to main content
Glama
SurfRankAI

SurfRank MCP Server

by SurfRankAI
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

add_competitor

Add a competitor domain to a project for side-by-side visibility tracking.

Instructions

Add a competitor domain to a project for side-by-side visibility tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes
domainYesCompetitor root domain
nameNoDisplay name (optional)

Implementation Reference

  • src/tools/competitors.js:14-28 (handler)
    The 'add_competitor' tool definition with its inputSchema and handler function. The handler makes a POST request to `/projects/{projectId}/competitors` with the domain (and optional name) body.
    {
  name: 'add_competitor',
  description: 'Add a competitor domain to a project for side-by-side visibility tracking.',
  inputSchema: {
    type: 'object',
    properties: {
      projectId: { type: 'string' },
      domain: { type: 'string', description: 'Competitor root domain' },
      name: { type: 'string', description: 'Display name (optional)' },
    },
    required: ['projectId', 'domain'],
  },
  handler: async ({ projectId, ...body }) =>
    api.post(`/projects/${projectId}/competitors`, body),
},
  • src/tools/competitors.js:17-25 (schema)
    Input schema for 'add_competitor': requires projectId (string) and domain (string), with an optional name (string).
    inputSchema: {
  type: 'object',
  properties: {
    projectId: { type: 'string' },
    domain: { type: 'string', description: 'Competitor root domain' },
    name: { type: 'string', description: 'Display name (optional)' },
  },
  required: ['projectId', 'domain'],
},
  • src/index.js:28-28 (registration)
    Import of competitorTools from the competitors.js module.
    import { competitorTools } from './tools/competitors.js';
  • src/index.js:37-37 (registration)
    Spread of competitorTools into the ALL_TOOLS array to register all competitor tools, including 'add_competitor'.
    ...competitorTools,

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions 'add' implying mutation, but does not disclose idempotency, duplicate behavior, permissions, or side effects. Insufficient for a mutation operation.

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, concise and front-loaded. The content is relevant and earns its place, though slightly more detail could be added without harming conciseness.

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?

No output schema and no description of return value or side effects. For a simple add operation, more context on success criteria or result is needed for complete understanding.

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 coverage is 67%, with projectId lacking description. The tool description adds no parameter details beyond the schema. It does not compensate for the missing parameter description.

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 verb 'Add', the resource 'competitor domain', and the context 'to a project for side-by-side visibility tracking'. It effectively differentiates from sibling tools like delete_competitor and list_competitors.

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, no prerequisites or exclusions mentioned. The implication of adding to a project is present but not elaborated.

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