Skip to main content
Glama
bruhsb
by bruhsb

paperclip_update_project

DestructiveIdempotent

Update project details such as name, description, or status by providing the project ID. Use to rename, change description, or archive a project.

Instructions

Update a project's name, description, or status.

Args:

  • projectId: string — Project UUID (example: "prj_abc123")

  • name: string (optional) — New name

  • description: string (optional) — New description (markdown)

  • status: string (optional) — New status (example: "archived")

Returns: Returns the updated project object with all fields.

Examples:

  • Use when: archiving a completed project or renaming it after a scope change

  • Don't use when: you need to update workspace settings — use paperclip_update_workspace instead

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 404: project not found → verify ID with paperclip_list_projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject UUID
nameNoNew name
descriptionNoNew description (markdown)
statusNoNew status (e.g. active, archived)
Behavior4/5

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

Annotations already provide destructiveHint=true and idempotentHint=true. Description adds error handling (401, 404) and return format (updated project object), but does not mention side effects beyond annotations.

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?

Description is front-loaded with purpose, structured into Args, Returns, Examples, Error Handling sections, and every sentence adds value without redundancy.

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 no output schema, description explains return value and includes error handling. It is fully sufficient for an agent to correctly invoke the tool.

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%. Description adds value with examples (e.g., 'prj_abc123', 'archived'), marks optional parameters, and clarifies status meaning (e.g., active, archived).

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?

Description explicitly states verb 'Update', resource 'project', and lists the specific fields (name, description, status). It clearly distinguishes from sibling tool paperclip_update_workspace.

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?

Description provides explicit 'Use when' (archiving, renaming) and 'Don't use when' (update workspace settings) examples, naming the alternative tool paperclip_update_workspace.

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/bruhsb/paperclip-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server