Skip to main content
Glama

update_person

Modify contact information in Copper CRM by updating job titles, tags, or the 'About' section. Specify only the fields you need to change.

Instructions

Update an existing person (contact) in Copper CRM. Only include fields you want to change. The 'details' field is the 'About' section visible at the top of the contact page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idYesCopper person ID to update
detailsNoAbout/details text (visible at top of contact page in Copper UI)
titleNoJob title
tagsNoTags (replaces existing tags)

Implementation Reference

  • Handler function for the update_person tool, which makes a PUT request to the Copper API.
    async ({ person_id, details, title, tags }) => {
      const body = {};
      if (details !== undefined) body.details = details;
      if (title !== undefined) body.title = title;
      if (tags !== undefined) body.tags = tags;
    
      const result = await copperFetch(`/people/${person_id}`, { method: "PUT", body });
      return jsonResult({
        id: result.id,
        name: result.name,
        details: result.details,
        title: result.title,
        tags: result.tags,
      });
    }
  • server.js:165-173 (registration)
    Registration of the update_person tool including its schema definition.
    server.tool(
      "update_person",
      "Update an existing person (contact) in Copper CRM. Only include fields you want to change. The 'details' field is the 'About' section visible at the top of the contact page.",
      {
        person_id: z.number().describe("Copper person ID to update"),
        details: z.string().optional().describe("About/details text (visible at top of contact page in Copper UI)"),
        title: z.string().optional().describe("Job title"),
        tags: z.array(z.string()).optional().describe("Tags (replaces existing tags)"),
      },
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that updates are partial (only include fields to change) and that tags replace existing ones, which are useful behavioral traits. However, it misses critical details like authentication needs, error handling, or whether changes are reversible.

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?

The description is appropriately sized with two sentences that are front-loaded and efficient. The first sentence states the purpose, and the second adds useful context about field behavior, with no wasted words.

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 and no output schema, the description is moderately complete. It covers partial updates and field specifics, but lacks information on return values, error cases, or system constraints like rate limits, leaving gaps for an AI agent.

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 description coverage is 100%, so the schema already documents all parameters well. The description adds minimal value by clarifying the 'details' field corresponds to the 'About' section in the UI, but doesn't provide additional syntax or format details beyond the schema.

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 clearly states the tool updates an existing person in Copper CRM, specifying it's for contacts. It distinguishes from create_person by focusing on updates, but doesn't explicitly contrast with other sibling tools like get_person or search_people.

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 implies usage for updating existing contacts and mentions to 'only include fields you want to change,' which provides some guidance. However, it lacks explicit when-to-use vs. alternatives (e.g., create_person for new contacts, get_person for reading) or prerequisites like required permissions.

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/dazanza/copper-mcp'

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