Skip to main content
Glama
SurfRankAI

SurfRank MCP Server

by SurfRankAI

list_competitors

Retrieve all competitors tracked for a given project to analyze competitive landscape.

Instructions

List all tracked competitors for a project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes

Implementation Reference

  • The handler function that executes the list_competitors tool logic. It calls api.get to fetch competitors for a given projectId.
    handler: async ({ projectId }) => api.get(`/projects/${projectId}/competitors`),
  • Input schema for list_competitors: requires a projectId string parameter.
    inputSchema: {
      type: 'object',
      properties: { projectId: { type: 'string' } },
      required: ['projectId'],
    },
  • Tool definition object including name, description, inputSchema, and handler for list_competitors, exported in the competitorTools array.
    {
      name: 'list_competitors',
      description: 'List all tracked competitors for a project.',
      inputSchema: {
        type: 'object',
        properties: { projectId: { type: 'string' } },
        required: ['projectId'],
      },
      handler: async ({ projectId }) => api.get(`/projects/${projectId}/competitors`),
    },
  • src/index.js:31-39 (registration)
    The list_competitors tool is registered into the ALL_TOOLS array via spread of competitorTools.
    const ALL_TOOLS = [
      ...projectTools,
      ...keywordTools,
      ...reportTools,
      ...quickTestTools,
      ...keywordResearchTools,
      ...competitorTools,
      ...opportunityTools,
    ];
  • src/index.js:67-78 (registration)
    The MCP CallTool handler looks up list_competitors from toolByName map and invokes its handler.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args = {} } = request.params;
      const tool = toolByName.get(name);
      if (!tool) {
        return {
          isError: true,
          content: [{ type: 'text', text: `Unknown tool: ${name}` }],
        };
      }
    
      try {
        const result = await tool.handler(args);
Behavior3/5

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

Given no annotations, the description could disclose more about behavior like return format, pagination, or error handling. It implies a read operation but lacks details.

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?

Single sentence, no unnecessary words. Perfectly concise for a simple list tool.

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?

Despite low complexity, missing context on return values, error scenarios, and usage context. Incomplete for an agent to use safely.

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?

With 0% schema coverage, the description only hints at the projectId parameter ("for a project") but adds no detail about its format, source, or validation.

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 (list), resource (competitors), and scope (for a project). It effectively distinguishes from siblings like add_competitor or delete_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 like list_keywords or list_projects. No mention of prerequisites or context such as requiring the project to exist.

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