Skip to main content
Glama
SurfRankAI

SurfRank MCP Server

by SurfRankAI

list_quick_tests

List quick tests to review AI visibility analytics. Filter by project for targeted results.

Instructions

List quick tests, optionally filtered by project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
websiteIdNoFilter to a specific project (optional)

Implementation Reference

  • Handler function for the 'list_quick_tests' tool — makes a GET request to '/quick-test' with optional websiteId query parameter.
    handler: async ({ websiteId }) => api.get('/quick-test', { websiteId }),
  • Input schema for 'list_quick_tests' — accepts an optional websiteId string filter.
    inputSchema: {
      type: 'object',
      properties: {
        websiteId: { type: 'string', description: 'Filter to a specific project (optional)' },
      },
    },
  • Tool definition object for 'list_quick_tests' — registered with name, description, inputSchema, and handler.
    {
      name: 'list_quick_tests',
      description: 'List quick tests, optionally filtered by project.',
      inputSchema: {
        type: 'object',
        properties: {
          websiteId: { type: 'string', description: 'Filter to a specific project (optional)' },
        },
      },
      handler: async ({ websiteId }) => api.get('/quick-test', { websiteId }),
    },
  • The api.get helper used by the handler to make a GET request to the SurfRank 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),
    };
  • src/index.js:31-39 (registration)
    Registration of quickTestTools (which includes list_quick_tests) into the ALL_TOOLS array for the MCP server.
    const ALL_TOOLS = [
      ...projectTools,
      ...keywordTools,
      ...reportTools,
      ...quickTestTools,
      ...keywordResearchTools,
      ...competitorTools,
      ...opportunityTools,
    ];
Behavior2/5

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

No annotations exist, and the description does not disclose whether the tool is read-only, pagination behavior, or any limitations. For a simple list tool, the bare minimum is stated, but no deeper behavioral insights are provided.

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 effectively communicates the core functionality without excess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one optional parameter, no output schema), the description is largely sufficient. However, it could mention what fields are returned (e.g., names, projects) for better completeness, but overall it's adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds context by saying 'optionally filtered by project,' which aligns with the parameter description. Baseline score is appropriate as the schema already defines the parameter adequately.

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 'quick tests', with explicit mention of optional filtering by project. This distinguishes it from sibling tools like 'get_quick_test' (singular) and 'list_projects' (different resource).

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 (e.g., 'get_quick_test' for a single test, 'list_reports' for reports). The description lacks context for decision-making.

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