Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

update_prompt

Partially update a tracked prompt by changing only selected fields—text, engines, country, language, or run cadence—while leaving omitted values unchanged and preserving its topic uniqueness.

Instructions

Partially update a tracked prompt — any combination of its text, engine list, country, response language or run cadence; omitted fields are left unchanged. The prompt keeps its current topic and must stay unique within it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose real behavior: partial-update semantics, that the topic cannot change here, and a uniqueness constraint that can cause failure. It omits any mention of required permissions, what error surface the uniqueness rule produces, or what the response contains.

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 compact sentences with the operation and partial-update rule front-loaded, followed by the two constraints. Nothing is redundant and the ordering matches what an agent needs to decide before calling.

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 mutation tool with no annotations, no output schema, and an untyped schema, the description covers the essential semantics but leaves gaps: no permission requirements, no error behavior for the uniqueness violation, and no field format guidance. Adequate but not fully self-sufficient.

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

Parameters4/5

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

The schema is effectively empty (additionalProperties only, no declared properties), so the description is the sole source of parameter knowledge, and it names the five mutable dimensions (text, engine list, country, response language, run cadence). It adds no format or type detail for engine list or cadence, which would be needed to actually construct a call.

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?

Uses a specific verb+resource ("Partially update a tracked prompt") and enumerates the mutable fields, which lets an agent distinguish it from a full replacement or a topic change. It also implicitly separates itself from update_prompt_topic by stating the prompt keeps its current topic, though it never names that sibling.

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?

The description conveys the key usage context — partial update, omitted fields unchanged, topic immutable, uniqueness within topic required — but never states explicitly when to prefer this over update_prompt_topic or a delete/create cycle. Guidance is implied rather than stated.

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

Deploy Server

Other Tools