Skip to main content
Glama
SurfRankAI

SurfRank MCP Server

by SurfRankAI

list_keywords

List all tracked keywords for a specific project to review your AI visibility monitoring targets.

Instructions

List all tracked keywords (prompts) for a project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes

Implementation Reference

  • Handler function for list_keywords: calls api.get(`/projects/${projectId}/keywords`) to list all tracked keywords for a project.
    handler: async ({ projectId }) => api.get(`/projects/${projectId}/keywords`),
  • Input schema for list_keywords: requires a projectId (string) parameter.
    inputSchema: {
      type: 'object',
      properties: { projectId: { type: 'string' } },
      required: ['projectId'],
    },
  • src/index.js:31-33 (registration)
    keywordTools array (containing list_keywords) is spread into ALL_TOOLS, registering the tool with the MCP server.
    const ALL_TOOLS = [
      ...projectTools,
      ...keywordTools,
  • src/index.js:24-24 (registration)
    Import of keywordTools from ./tools/keywords.js into the main server entry point.
    import { keywordTools } from './tools/keywords.js';
  • The api object providing the .get() method used by list_keywords handler; delegates to request() which calls fetch().
    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 exist, so the description must disclose behavioral traits. It only states 'list all' without mentioning pagination, read-only nature, rate limits, or authentication requirements.

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?

The description is a single sentence that is front-loaded and efficient. However, it could include more detail without becoming verbose.

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?

For a simple listing tool with one required parameter and no output schema, the description is adequate but lacks details on pagination, ordering, or expected response format.

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 0%, and the description adds minimal meaning beyond the schema: it says 'for a project' but does not explain what projectId represents or any format constraints.

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 'list' and the resource 'tracked keywords (prompts)' with scope 'for a project', effectively distinguishing it from sibling tools like add_keyword or delete_keyword.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The purpose is implied but there is no mention of alternatives or context for selection among siblings.

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