SurfRank MCP Server

update_project

Update an existing project by modifying only the fields you want to change, such as brand name, industry, or country.

Instructions

Update an existing project. Pass only the fields you want to change.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	Yes
`brandName`	No
`industry`	No
`country`	No

Implementation Reference

src/tools/projects.js:58-58 (handler)
Handler for 'update_project' tool — destructures projectId and remaining fields, then sends a PATCH request to /projects/:id.
```
handler: async ({ projectId, ...patch }) => api.patch(`/projects/${projectId}`, patch),
```

src/tools/projects.js:48-57 (schema)

Input schema for 'update_project' — accepts projectId (required) plus optional fields: brandName, industry, country.

inputSchema: {
  type: 'object',
  properties: {
    projectId: { type: 'string' },
    brandName: { type: 'string' },
    industry: { type: 'string' },
    country: { type: 'string' },
  },
  required: ['projectId'],
},

src/tools/projects.js:45-59 (registration)

Tool object definition registered in the projectTools array, which is spread into ALL_TOOLS in src/index.js.

{
  name: 'update_project',
  description: 'Update an existing project. Pass only the fields you want to change.',
  inputSchema: {
    type: 'object',
    properties: {
      projectId: { type: 'string' },
      brandName: { type: 'string' },
      industry: { type: 'string' },
      country: { type: 'string' },
    },
    required: ['projectId'],
  },
  handler: async ({ projectId, ...patch }) => api.patch(`/projects/${projectId}`, patch),
},

src/index.js:31-41 (registration)

ALL_TOOLS array in src/index.js — projectTools (including update_project) are spread into the full tool list.

const ALL_TOOLS = [
  ...projectTools,
  ...keywordTools,
  ...reportTools,
  ...quickTestTools,
  ...keywordResearchTools,
  ...competitorTools,
  ...opportunityTools,
];

const toolByName = new Map(ALL_TOOLS.map((t) => [t.name, t]));

src/client.js:81-81 (helper)
The api.patch method used by the update_project handler to call the SurfRank API.
```
patch: (path, body) => request('PATCH', path, { body }),
```

Tool Definition Quality

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It indicates an update operation but does not disclose whether omitted fields are preserved or reset, or any permissions required. The partial update instruction is helpful but insufficient for full transparency.

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 two short sentences with no wasted words. It is front-loaded with the key action and usage pattern.

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?

The description is minimal. For a mutation tool with no output schema, it could mention return value or confirmation. It does not cover permissions or limits. However, the tool is simple with 4 parameters and no nested objects, so it meets a basic threshold.

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 description coverage is 0%, and the description adds no specific meaning to individual parameters (projectId, brandName, industry, country). The generic 'pass only fields you want to change' does not explain what each field does or its 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 'Update' and the resource 'existing project'. It also specifies partial update behavior ('Pass only the fields you want to change'). This distinguishes it from sibling tools like create_project and delete_project.

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?

The description provides guidance on how to use the tool (pass only fields to change) but does not explicitly mention when to use it versus alternatives like create_project. However, the context of sibling tools makes the distinction clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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