Skip to main content
Glama
SurfRankAI

SurfRank MCP Server

by SurfRankAI

list_opportunities

Identify content and keyword opportunities flagged for a project, showing under-mention relative to competitors, ranked by expected impact.

Instructions

List content / keyword opportunities flagged for a project — prompts where the brand is under-mentioned relative to competitors, ranked by expected impact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes
statusNoFilter by status (e.g. "open", "addressed"). Optional.
sortByNoSort field (optional)
pageNo
limitNo

Implementation Reference

  • The handler function that executes the list_opportunities tool logic. It calls api.get(`/projects/${projectId}/opportunities`, query) to fetch opportunities from the SurfRank API.
    handler: async ({ projectId, ...query }) =>
      api.get(`/projects/${projectId}/opportunities`, query),
  • Input schema for list_opportunities: requires projectId, with optional status, sortBy, page, and limit parameters.
    inputSchema: {
      type: 'object',
      properties: {
        projectId: { type: 'string' },
        status: {
          type: 'string',
          description: 'Filter by status (e.g. "open", "addressed"). Optional.',
        },
        sortBy: { type: 'string', description: 'Sort field (optional)' },
        page: { type: 'number' },
        limit: { type: 'number' },
      },
      required: ['projectId'],
  • src/index.js:29-38 (registration)
    Import and registration of opportunityTools (including list_opportunities) into the ALL_TOOLS array and toolByName map on the MCP server.
    import { opportunityTools } from './tools/opportunities.js';
    
    const ALL_TOOLS = [
      ...projectTools,
      ...keywordTools,
      ...reportTools,
      ...quickTestTools,
      ...keywordResearchTools,
      ...competitorTools,
      ...opportunityTools,
  • The api.get helper method used by the handler, which calls the low-level request function with HTTP GET.
    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),
    };
Behavior3/5

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

With no annotations, the description carries full burden; it states 'list' implying read-only but lacks explicit mention of side effects, auth needs, or pagination behavior.

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, front-loaded with verb, no waste; efficiently conveys purpose.

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?

Given no output schema and multiple sibling list tools, the description outlines the tool's purpose but omits return format and pagination hints, making it minimally adequate.

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 low (40%) and the description adds no parameter details beyond implying projectId context; it does not clarify status, sortBy, page, or limit.

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 tool lists opportunities, defines them as under-mentioned prompts ranked by impact, and distinguishes from sibling list tools by specifying opportunity-specific content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for viewing opportunities but provides no explicit guidance on when not to use or alternatives such as list_keywords or list_competitors.

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