Skip to main content
Glama

Visibility Genies

Restore a project

restore_project

Restores an archived project and its saved data to the active project list. The call itself is free and buys no data; previously enabled schedules may resume and spend under their existing approvals. Pass archivedProjectId from list_archived_projects. Requires project deletion rights, as archiving does. A project whose permanent deletion has started cannot be restored.

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": {
      "archivedProjectId": "<archivedProjectId>"
    },
    "name": "restore_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
archivedProjectIdYesThe id returned by list_archived_projects.

Output Schema

NameRequiredDescriptionDefault
successYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the call itself is free but that previously enabled schedules may resume and spend under existing approvals, which is a real cost side-effect not captured by destructiveHint=false. It also adds an authorization requirement and a hard failure condition. This is the kind of context an agent cannot get from the structured fields.

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?

Front-loads the action and its effect, then adds prerequisites and caveats in short, information-dense clauses; every sentence earns its place. The only minor waste is the restatement of the archivedProjectId sourcing already present in the schema.

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?

For a one-parameter mutation with an output schema, the description covers everything an agent needs before calling: required permission, cost and spend implications, the blocking deletion state, and id provenance. Return values are correctly left to the output schema.

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 single parameter already documents that the id comes from list_archived_projects. The description's "Pass archivedProjectId from list_archived_projects" restates that rather than adding format or sourcing detail, so the baseline of 3 is appropriate.

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?

States a specific verb and resource ("Restores an archived project and its saved data to the active project list"), which is far more precise than the title. It implicitly separates itself from archive_project by naming the inverse operation and from restore_action by scoping to projects, but it never names those siblings explicitly, so an agent must infer the boundary.

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

Usage Guidelines5/5

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

Gives explicit prerequisites ("Requires project deletion rights, as archiving does"), a concrete exclusion ("A project whose permanent deletion has started cannot be restored"), and tells the agent where the id comes from (list_archived_projects). When-to-use and when-not-to-use are both covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources