Skip to main content
Glama

list_activities

Search and filter Copper CRM activities including meeting notes, calls, and emails by parent record, activity type, or date range. Returns resolved parent names with pagination support.

Instructions

Search Copper activities (meeting notes, calls, emails logged against contacts). Filter by parent record, activity type, or date range. Returns resolved parent names. Excludes system activities (assignee/status changes) by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_typeNoFilter by parent entity type
parent_idNoFilter by parent entity ID (requires parent_type)
minimum_activity_dateNoUnix timestamp — only activities on or after this date
maximum_activity_dateNoUnix timestamp — only activities on or before this date
include_systemNoInclude system activities like assignee/status changes (default: false)
page_sizeNoResults per page (default 20, max 200)
page_numberNoPage number (default 1)

Implementation Reference

  • Registration and implementation of the 'list_activities' tool, including input schema definition and the handler function logic.
    server.tool(
      "list_activities",
      "Search Copper activities (meeting notes, calls, emails logged against contacts). Filter by parent record, activity type, or date range. Returns resolved parent names. Excludes system activities (assignee/status changes) by default.",
      {
        parent_type: z.enum(["person", "company", "lead", "opportunity", "project", "task"]).optional().describe("Filter by parent entity type"),
        parent_id: z.number().optional().describe("Filter by parent entity ID (requires parent_type)"),
        minimum_activity_date: z.number().optional().describe("Unix timestamp — only activities on or after this date"),
        maximum_activity_date: z.number().optional().describe("Unix timestamp — only activities on or before this date"),
        include_system: z.boolean().optional().describe("Include system activities like assignee/status changes (default: false)"),
        page_size: z.number().optional().describe("Results per page (default 20, max 200)"),
        page_number: z.number().optional().describe("Page number (default 1)"),
      },
      async ({ parent_type, parent_id, minimum_activity_date, maximum_activity_date, include_system, page_size, page_number }) => {
        const body = {};
        if (parent_type && parent_id) body.parent = { id: parent_id, type: parent_type };
        if (minimum_activity_date) body.minimum_activity_date = minimum_activity_date;
        if (maximum_activity_date) body.maximum_activity_date = maximum_activity_date;
        body.page_size = page_size || 200;
        body.page_number = page_number || 1;
    
        const results = await copperFetch("/activities/search", { method: "POST", body });
    
        // Filter out system activities unless explicitly requested
        const filtered = include_system
          ? results
          : results.filter((a) => a.type?.category === "user");
    
        // Resolve parent names
        const nameCache = new Map();
        const activities = await Promise.all(
          filtered.map(async (a) => {
            const parentType = a.parent?.type;
            const parentId = a.parent?.id;
            const parent_name = parentType && parentId
              ? await resolveParentName(parentType, parentId, nameCache)
              : null;
    
            return {
              id: a.id,
              parent: a.parent,
              parent_name,
              type: a.type,
              user_id: a.user_id,
              details: a.details,
              activity_date: a.activity_date,
              date_created: a.date_created,
              date_modified: a.date_modified,
            };
          })
        );
    
        return jsonResult(activities);
      }
    );
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses useful behavioral traits: what gets returned ('Returns resolved parent names'), what's excluded by default ('Excludes system activities'), and pagination behavior is implied through parameters. However, it doesn't mention rate limits, authentication requirements, error conditions, or whether this is a read-only operation (though 'Search' implies it).

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 perfectly concise with three information-dense sentences. The first sentence establishes purpose and scope, the second explains filtering capabilities, and the third covers return values and exclusions. Every sentence earns its place with zero 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 search/list tool with 7 parameters, 100% schema coverage, but no annotations and no output schema, the description is adequate but has gaps. It covers purpose, filtering, exclusions, and return values, but doesn't address authentication, error handling, rate limits, or provide examples of the output format. The lack of output schema means the description should ideally say more about what the response looks like.

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 7 parameters thoroughly. The description adds marginal value by mentioning the filtering capabilities ('Filter by parent record, activity type, or date range') and the default exclusion behavior, but doesn't provide additional parameter semantics beyond what's in the schema descriptions.

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 verb ('Search') and resource ('Copper activities') with specific examples of what activities include ('meeting notes, calls, emails logged against contacts'). It distinguishes from siblings by focusing on listing/searching activities rather than creating them (create_activity) or managing other entities like people/companies.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool ('Filter by parent record, activity type, or date range') and mentions what it excludes ('Excludes system activities... by default'). However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools for different filtering needs.

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