Skip to main content
Glama

create_activity

Log meetings, calls, or notes against contacts or companies in Copper CRM. Use this tool to record activity details and maintain customer relationship records.

Instructions

Log an activity (meeting note, phone call, etc.) against a Copper person or company. Use list_activity_types first to get the correct activity_type_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_typeYesType of record to log against
parent_idYesCopper ID of the person or company
activity_type_idYesActivity type ID (from list_activity_types)
detailsYesActivity content — meeting notes, action items, summary, etc. Use plain text, not markdown.
activity_dateNoUnix timestamp for when the activity occurred (default: now)

Implementation Reference

  • The registration and implementation handler for the "create_activity" tool.
    server.tool(
      "create_activity",
      "Log an activity (meeting note, phone call, etc.) against a Copper person or company. Use list_activity_types first to get the correct activity_type_id.",
      {
        parent_type: z.enum(["person", "company"]).describe("Type of record to log against"),
        parent_id: z.number().describe("Copper ID of the person or company"),
        activity_type_id: z.number().describe("Activity type ID (from list_activity_types)"),
        details: z.string().describe("Activity content — meeting notes, action items, summary, etc. Use plain text, not markdown."),
        activity_date: z.number().optional().describe("Unix timestamp for when the activity occurred (default: now)"),
      },
      async ({ parent_type, parent_id, activity_type_id, details, activity_date }) => {
        const body = {
          parent: { type: parent_type, id: parent_id },
          type: { id: activity_type_id, category: "user" },
          user_id: parseInt(USER_ID),
          details,
        };
        if (activity_date) body.activity_date = activity_date;
    
        const result = await copperFetch("/activities", { method: "POST", body });
        return jsonResult({
          id: result.id,
          parent: result.parent,
          type: result.type,
          details: result.details,
          activity_date: result.activity_date,
        });
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions logging an activity but doesn't disclose behavioral traits like whether this is a write operation (implied by 'Log'), potential side effects, authentication needs, error handling, or response format. For a mutation tool with zero annotation coverage, this is a significant gap.

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 front-loaded with the core purpose in the first sentence, and the second sentence provides essential usage guidance without redundancy. Every sentence earns its place, making it appropriately sized and efficient.

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?

Given the tool's complexity (a mutation with 5 parameters) and no annotations or output schema, the description is incomplete. It covers purpose and usage well but lacks behavioral context (e.g., what happens on success/failure) and output details. It's adequate as a minimum viable description but has clear gaps.

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 thoroughly. The description adds minimal value beyond the schema by hinting at the need to use list_activity_types for activity_type_id and specifying plain text for details, but it doesn't provide additional syntax or format details. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description clearly states the specific action ('Log an activity') and the target resource ('against a Copper person or company'), with examples of activity types. It distinguishes from siblings like list_activities (which retrieves) and create_person (which creates a different entity).

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?

It explicitly provides when-to-use guidance by directing the user to 'Use list_activity_types first to get the correct activity_type_id,' which is a prerequisite step. This distinguishes it from tools like list_activities that don't require such preparation.

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