Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

update_contact

Modify contact details in Apollo.io's B2B sales platform to maintain accurate prospect information for sales operations.

Instructions

Update an existing contact's information in Apollo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact ID
first_nameNoFirst name
last_nameNoLast name
emailNoEmail address
titleNoJob title
linkedin_urlNoLinkedIn URL

Implementation Reference

  • The core handler function that destructures the args to separate id and updateData, makes a PUT request to Apollo API endpoint `/contacts/${id}` with the update data, and returns a success message with the updated contact's ID and name.
    private async updateContact(args: any) {
      const { id, ...updateData } = args;
      const response = await this.axiosInstance.put(`/contacts/${id}`, updateData);
      const contact = response.data.contact;
    
      return {
        content: [
          {
            type: "text",
            text: `Contact updated successfully!\nID: ${contact.id}\nName: ${contact.first_name} ${contact.last_name}`,
          },
        ],
      };
    }
  • The input schema definition for the update_contact tool, specifying the required 'id' parameter and optional fields for updating contact details like name, email, title, and LinkedIn URL.
    {
      name: "update_contact",
      description: "Update an existing contact's information in Apollo.",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "Contact ID",
          },
          first_name: {
            type: "string",
            description: "First name",
          },
          last_name: {
            type: "string",
            description: "Last name",
          },
          email: {
            type: "string",
            description: "Email address",
          },
          title: {
            type: "string",
            description: "Job title",
          },
          linkedin_url: {
            type: "string",
            description: "LinkedIn URL",
          },
        },
        required: ["id"],
      },
    },
  • src/index.ts:90-91 (registration)
    The switch case registration that maps incoming tool calls with name 'update_contact' to the execution of the updateContact handler method.
    case "update_contact":
      return await this.updateContact(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Update' implies a mutation, it doesn't specify required permissions, whether changes are reversible, rate limits, or what happens to fields not mentioned. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 gets straight to the point with zero wasted words. It's appropriately sized for a straightforward update operation and front-loads the essential information.

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?

Given this is a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address error conditions, response format, or behavioral constraints that would help an agent use it correctly. The high schema coverage helps with parameters, but other contextual gaps remain.

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?

The schema description coverage is 100%, so the schema already documents all 6 parameters thoroughly. The description doesn't add any parameter-specific context beyond what's in the schema (e.g., format constraints, validation rules), so it meets the baseline for high schema coverage.

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 ('Update') and resource ('existing contact's information in Apollo'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'create_contact' by specifying it's for existing contacts, though it doesn't explicitly differentiate from other potential update operations.

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. It doesn't mention prerequisites (e.g., needing a contact ID), when not to use it, or how it differs from similar tools like 'create_contact' beyond the obvious 'existing' versus 'new' distinction.

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/masridigital/apollo.io-mcp'

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