Skip to main content
Glama
SurfRankAI

SurfRank MCP Server

by SurfRankAI

trigger_report

Queue an AI-visibility report for a project. Costs 0.3 credits per keyword per engine, returns a job ID instantly.

Instructions

Queue a new AI-visibility report for a project. Cost: 0.3 credits × keywords × engines. Returns immediately with a job ID (202). Poll get_report or list_reports to check status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes

Implementation Reference

  • The handler function for trigger_report - makes a POST request to /projects/{projectId}/reports/trigger using the api client.
    handler: async ({ projectId }) => api.post(`/projects/${projectId}/reports/trigger`),
  • Input schema for trigger_report - expects an object with a required 'projectId' string property.
    inputSchema: {
      type: 'object',
      properties: { projectId: { type: 'string' } },
      required: ['projectId'],
    },
  • src/index.js:31-41 (registration)
    Registration of reportTools (which includes trigger_report) into the ALL_TOOLS array, then indexed by name in a Map for dispatch.
    const ALL_TOOLS = [
      ...projectTools,
      ...keywordTools,
      ...reportTools,
      ...quickTestTools,
      ...keywordResearchTools,
      ...competitorTools,
      ...opportunityTools,
    ];
    
    const toolByName = new Map(ALL_TOOLS.map((t) => [t.name, t]));
  • The api helper object providing post() used by the trigger_report handler to make the HTTP request.
    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),
    };
Behavior4/5

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

Discloses queuing behavior, immediate return, job ID, status 202, and cost; no annotations exist so description carries full burden.

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?

Two efficient sentences: first states purpose, second adds cost, return behavior, and next steps with no waste.

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?

Adequately covers purpose, return, and next steps for a simple trigger tool with one parameter and no output schema; lacks error handling details.

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?

Only one parameter 'projectId' with no schema description; description does not elaborate on the parameter beyond schema, but parameter is self-explanatory.

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?

States specifically that it queues a new AI-visibility report for a project, distinguishing from siblings like 'get_report' which polls status.

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

Usage Guidelines4/5

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

Provides cost formula, return behavior (immediate with job ID and 202 status), and explicitly mentions polling alternatives 'get_report' or 'list_reports'.

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