Skip to main content
Glama
SurfRankAI

SurfRank MCP Server

by SurfRankAI

get_keyword_research

Retrieve a specific keyword research run by its ID to analyze AI visibility data and insights.

Instructions

Get a single keyword-research run by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
researchIdYes

Implementation Reference

  • Tool definition and handler for 'get_keyword_research'. The handler calls api.get('/keyword-research/${researchId}') to fetch a single keyword-research run by its ID.
    {
      name: 'get_keyword_research',
      description: 'Get a single keyword-research run by ID.',
      inputSchema: {
        type: 'object',
        properties: { researchId: { type: 'string' } },
        required: ['researchId'],
      },
      handler: async ({ researchId }) => api.get(`/keyword-research/${researchId}`),
    },
  • Input schema for 'get_keyword_research'. Expects an object with a required 'researchId' (string) property.
    inputSchema: {
      type: 'object',
      properties: { researchId: { type: 'string' } },
      required: ['researchId'],
    },
  • src/index.js:27-36 (registration)
    Imports and spreads keywordResearchTools into ALL_TOOLS, registering 'get_keyword_research' (along with the other keyword research tools) with the MCP server.
    import { keywordResearchTools } from './tools/keywordResearch.js';
    import { competitorTools } from './tools/competitors.js';
    import { opportunityTools } from './tools/opportunities.js';
    
    const ALL_TOOLS = [
      ...projectTools,
      ...keywordTools,
      ...reportTools,
      ...quickTestTools,
      ...keywordResearchTools,
  • The api.get() method used by the handler. Delegates to the generic request() function to make a GET request to the SurfRank public API.
    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?

With no annotations, the description must fully communicate behavioral traits. It only says 'get,' implying a read-only operation, but no details about side effects, permissions, or response characteristics are given.

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?

The description is a single, concise sentence with no redundant information. It efficiently conveys the tool's function.

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 lack of output schema and the simplicity of the tool, the description should at least hint at the structure or content of the returned keyword-research run. It does not, leaving the agent uninformed about the result format.

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 input schema has 0% description coverage, meaning 'researchId' has no documentation. The description does not add any meaning or constraints beyond the schema, failing to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (get) and resource (single keyword-research run by ID). It is specific enough to distinguish from list operations, but does not explicitly differentiate from sibling tools like list_keyword_research.

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. There is no mention of prerequisites, when not to use it, or comparisons to related tools.

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