Skip to main content
Glama

Edit project

update_project
Idempotent

Rename a project and update its AI brief, automatic rank-check schedule, or mine/competitor status to keep keyword tracking and history accurate.

Instructions

Rename a project, change its brief (context used by the AI), its automatic rank-check schedule, or whether it is the owner's app (mine) or a competitor (keeps keywords and history).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "update_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNomine = an app the owner publishes; competitor = someone else's.
nameNoDisplay name.
briefNoShort description of the app used by the AI.
autoCheckNoAutomatic check schedule (inherit = global setting).
projectIdYesProject id (from get_overview).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.12
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "mine = an app the owner publishes; competitor = someone else's.",
      +  "enum": [
      +    "mine",
      +    "competitor"
      +  ],
      +  "type": "string"
      +}
  2. First observedv0.1.7

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the safety bar is low. The description nonetheless adds real behavioral context: brief is "context used by the AI," and switching kind to competitor "keeps keywords and history," which tells the agent a kind change is non-destructive to data. It does not address permission requirements or what happens to omitted fields, keeping it out of 5 territory.

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?

A single sentence that front-loads the core action and then enumerates the editable fields in order of importance. Every clause corresponds to a parameter, so nothing is wasted, though the nested parentheticals make it slightly dense to parse.

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

Completeness5/5

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

With five flat parameters, one required, no output schema, and no destructive behavior, the description covers all editable fields and their notable side effects. Combined with annotations that carry the safety profile and a fully documented schema, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3 and the schema already documents each field including enum values. The description goes beyond it by explaining the consequence of the kind switch (keywords and history preserved) and the role of brief as AI context, which the schema descriptions do not convey. It adds marginal but genuine semantic value.

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?

The description opens with a specific verb and resource ("Rename a project") and enumerates the four editable attributes: name, brief, autoCheck schedule, and mine/competitor kind. An agent can immediately tell this edits existing project attributes rather than moving, removing, or resyncing a project. It stops short of naming a sibling it is not, so it falls just below a 5.

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?

Usage is implied by the enumerated fields — use this when you need to change a project's name, brief, check schedule, or kind. There is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g., project must exist, id from get_overview is only in the schema), and no routing away from near-neighbors like move_project or update_settings.

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