Skip to main content
Glama

create_person

Add new contacts to Copper CRM with details like name, company, email, phone, and tags to organize customer relationships.

Instructions

Create a new person (contact) in Copper CRM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
first_nameYesFirst name
last_nameYesLast name
titleNoJob title
company_nameNoCompany name (Copper auto-links or creates)
emailsNoEmail addresses
phone_numbersNoPhone numbers
tagsNoTags for categorization
contact_type_idNoContact type ID (e.g. Potential Customer)

Implementation Reference

  • server.js:129-162 (registration)
    Registration and handler implementation for the create_person tool.
    server.tool(
      "create_person",
      "Create a new person (contact) in Copper CRM.",
      {
        first_name: z.string().describe("First name"),
        last_name: z.string().describe("Last name"),
        title: z.string().optional().describe("Job title"),
        company_name: z.string().optional().describe("Company name (Copper auto-links or creates)"),
        emails: z.array(z.object({
          email: z.string(),
          category: z.enum(["work", "personal", "other"]).optional()
        })).optional().describe("Email addresses"),
        phone_numbers: z.array(z.object({
          number: z.string(),
          category: z.enum(["work", "mobile", "home", "other"]).optional()
        })).optional().describe("Phone numbers"),
        tags: z.array(z.string()).optional().describe("Tags for categorization"),
        contact_type_id: z.number().optional().describe("Contact type ID (e.g. Potential Customer)"),
      },
      async ({ first_name, last_name, title, company_name, emails, phone_numbers, tags, contact_type_id }) => {
        const body = { name: `${first_name} ${last_name}` };
        if (first_name) body.first_name = first_name;
        if (last_name) body.last_name = last_name;
        if (title) body.title = title;
        if (company_name) body.company_name = company_name;
        if (emails) body.emails = emails;
        if (phone_numbers) body.phone_numbers = phone_numbers;
        if (tags) body.tags = tags;
        if (contact_type_id) body.contact_type_id = contact_type_id;
    
        const result = await copperFetch("/people", { method: "POST", body });
        return jsonResult(result);
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation but doesn't mention important behavioral aspects: whether this requires specific permissions, what happens on duplicate entries, whether the operation is idempotent, what the response contains, or any rate limits. The description is minimal and leaves critical behavioral questions unanswered.

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?

The description is a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a creation tool and gets straight to the point with no unnecessary elaboration.

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

Completeness2/5

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

For a mutation tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation (return values, success indicators), doesn't mention error conditions, and provides no context about Copper CRM's specific behavior for person creation. The description leaves too many open questions for effective tool use.

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 8 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. The baseline score of 3 reflects adequate parameter documentation entirely through the schema, with no value added by the description.

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 action ('Create') and resource ('new person/contact in Copper CRM'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'update_person' or 'get_person' beyond the obvious creation vs. update/retrieval distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'update_person' or 'search_people'. There's no mention of prerequisites (e.g., whether the person must not already exist), nor any context about when creation is appropriate versus updating existing records.

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