Skip to main content
Glama

list_opportunities

Search and filter sales deals in Copper CRM to view opportunity details like name, value, status, and pipeline stage for tracking and management.

Instructions

Search Copper opportunities (deals). Optionally filter by company or person. Returns deal name, value, status, and pipeline stage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOpportunity name to search
company_idsNoFilter by company IDs
person_idsNoFilter by associated person IDs (custom field)
page_sizeNoResults per page (default 20, max 200)
page_numberNoPage number (default 1)

Implementation Reference

  • The handler function for 'list_opportunities' which processes inputs, fetches data from the Copper API, maps the results, and returns them.
    async ({ name, company_ids, person_ids, page_size, page_number }) => {
      const body = {};
      if (name) body.name = name;
      if (company_ids) body.company_ids = company_ids;
      if (person_ids) body.person_ids = person_ids;
      body.page_size = page_size || 20;
      body.page_number = page_number || 1;
    
      const results = await copperFetch("/opportunities/search", { method: "POST", body });
      const opps = results.map((o) => ({
        id: o.id,
        name: o.name,
        company_id: o.company_id,
        company_name: o.company_name,
        monetary_value: o.monetary_value,
        status: o.status,
        pipeline_id: o.pipeline_id,
        pipeline_stage_id: o.pipeline_stage_id,
        close_date: o.close_date,
        win_probability: o.win_probability,
      }));
      return jsonResult(opps);
    }
  • The Zod schema definition for the 'list_opportunities' tool inputs.
    {
      name: z.string().optional().describe("Opportunity name to search"),
      company_ids: z.array(z.number()).optional().describe("Filter by company IDs"),
      person_ids: z.array(z.number()).optional().describe("Filter by associated person IDs (custom field)"),
      page_size: z.number().optional().describe("Results per page (default 20, max 200)"),
      page_number: z.number().optional().describe("Page number (default 1)"),
    },
  • server.js:262-264 (registration)
    Registration of the 'list_opportunities' tool using server.tool.
    server.tool(
      "list_opportunities",
      "Search Copper opportunities (deals). Optionally filter by company or person. Returns deal name, value, status, and pipeline stage.",
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 mentions the search functionality and return fields but doesn't address important behaviors like pagination (implied by page parameters but not explained), rate limits, authentication requirements, error conditions, or whether this is a read-only operation. The description provides basic functional context but misses key operational details.

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 concise with two sentences that efficiently convey core functionality. The first sentence covers purpose and optional filtering, the second specifies return fields. No wasted words, though it could be slightly more structured for clarity.

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 tool with 5 parameters, 100% schema coverage, but no annotations or output schema, the description provides adequate basic context but has significant gaps. It explains what the tool does and what it returns, but doesn't address pagination behavior, result limitations, error handling, or how results are structured. The absence of output schema increases the need for more complete behavioral description.

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 5 parameters thoroughly. The description adds minimal value beyond the schema - it mentions optional filtering by company or person (which the schema covers) and implies search functionality for the 'name' parameter. No additional syntax, format details, or constraints beyond what the schema provides.

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 searches Copper opportunities (deals) and returns specific fields (deal name, value, status, pipeline stage). It uses specific verbs ('search', 'returns') and identifies the resource ('opportunities/deals'). However, it doesn't explicitly differentiate from sibling tools like 'search_companies' or 'search_people' beyond mentioning optional filtering by company/person.

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 searching opportunities with optional company/person filtering, but doesn't provide explicit guidance on when to use this versus alternatives like 'search_companies' or 'search_people'. No when-not-to-use scenarios or prerequisites are mentioned.

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