Skip to main content
Glama

AIsa Sales

by one.aisa
OverviewDiscussionsAdmin

Update or View Contact

patch_apollo_contacts_contact_id
Destructive

View a contact by ID. Requires a master API key.

Published reference price: $0.012 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
bodyYes
contact_idYesContact ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / account_id
      Removed value: -{
-  "description": "Account ID",
-  "type": "string"
-}
    • addedInput schema / properties / body
      Added value: +{
+  "properties": {
+    "account_id": {
+      "description": "Update the account ID. Example: `63f53afe4ceeca00016bdd2f`",
+      "type": "string"
+    },
+    "contact_stage_id": {
+      "description": "Update the contact stage ID. Example: `6095a710bd01d100a506d4af`",
+      "type": "string"
+    },
+    "corporate_phone": {
+      "description": "Work/office phone.",
+      "type": "string"
+    },
+    "direct_phone": {
+      "description": "Primary phone.",
+      "type": "string"
+    },
+    "email": {
+      "description": "Update the contact email. Example: `example@email.com`",
+      "type": "string"
+    },
+    "first_name": {
+      "description": "Update the contact's first name. Example: `Tim`",
+      "type": "string"
+    },
+    "home_phone": {
+      "description": "Home phone.",
+      "type": "string"
+    },
+    "label_names": {
+      "description": "Replace lists this contact belongs to. (Passing new values will overwrite existing lists.)",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "last_name": {
+      "description": "Update the contact's last name. Example: `Zheng`",
+      "type": "string"
+    },
+    "mobile_phone": {
+      "description": "Mobile phone.",
+      "type": "string"
+    },
+    "organization_name": {
+      "description": "Update the employer (company) name. Example: `apollo`",
+      "type": "string"
+    },
+    "other_phone": {
+      "description": "Alternate phone.",
+      "type": "string"
+    },
+    "present_raw_address": {
+      "description": "Update location (city/state/country). Example: `Atlanta, United States`",
+      "type": "string"
+    },
+    "title": {
+      "description": "Update the job title. Example: `senior research analyst`",
+      "type": "string"
+    },
+    "typed_custom_fields": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Add information to <a href=\"https://knowledge.apollo.io/hc/en-us/articles/4412498825869-Create-Custom-Contact-Fields\" target=\"_blank\">custom fields</a> in Apollo. <br><br><b>Your custom fields are unique to your team's Apollo account. This means that the examples in this documentation may not work for your testing purposes.</b> <br><br>To utilize this parameter successfully, call the <a href=\"https://docs.apollo.io/reference/get-a-list-of-all-custom-fields\">get a list of all custom fields</a> endpoint and identify the `id` value for the custom field, as well as the appropriate data type. For example, if a custom field accepts picklist entries, you need to pass the accompanying `id` value for the picklist entry that you want to use as the input value. <br><br><b>Example</b>: When the <a href=\"https://docs.apollo.io/reference/get-a-list-of-all-custom-fields\">get a list of all custom fields</a> endpoint returns an `id` of field: \n * `\"60c39ed82bd02f01154c470a\"` (datetime) \n \n\n then the value passed should be: \n\n `{\"60c39ed82bd02f01154c470a\": \"2025-08-07\"}`",
+      "example": {
+        "60c39ed82bd02f01154c470a": "2025-08-07"
+      },
+      "type": "object"
+    },
+    "website_url": {
+      "description": "Update the employer website URL. Example: `https://www.apollo.io/`",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / contact_stage_id
      Removed value: -{
-  "description": "Contact stage ID",
-  "type": "string"
-}
    • removedInput schema / properties / corporate_phone
      Removed value: -{
-  "description": "Corporate phone",
-  "type": "string"
-}
    • removedInput schema / properties / direct_phone
      Removed value: -{
-  "description": "Direct phone",
-  "type": "string"
-}
    • removedInput schema / properties / email
      Removed value: -{
-  "description": "Email",
-  "type": "string"
-}
    • removedInput schema / properties / first_name
      Removed value: -{
-  "description": "First name",
-  "type": "string"
-}
    • removedInput schema / properties / home_phone
      Removed value: -{
-  "description": "Home phone",
-  "type": "string"
-}
    • removedInput schema / properties / label_names
      Removed value: -{
-  "description": "Labels to set on the contact",
-  "type": "string"
-}
    • removedInput schema / properties / last_name
      Removed value: -{
-  "description": "Last name",
-  "type": "string"
-}
    • removedInput schema / properties / mobile_phone
      Removed value: -{
-  "description": "Mobile phone",
-  "type": "string"
-}
    • removedInput schema / properties / organization_name
      Removed value: -{
-  "description": "Organization name",
-  "type": "string"
-}
    • removedInput schema / properties / other_phone
      Removed value: -{
-  "description": "Other phone",
-  "type": "string"
-}
    • removedInput schema / properties / present_raw_address
      Removed value: -{
-  "description": "Raw address",
-  "type": "string"
-}
    • removedInput schema / properties / title
      Removed value: -{
-  "description": "Title",
-  "type": "string"
-}
    • removedInput schema / properties / typed_custom_fields
      Removed value: -{
-  "description": "Typed custom fields object",
-  "type": "object"
-}
    • removedInput schema / properties / website_url
      Removed value: -{
-  "description": "Website URL",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "contact_id"
-]New value: +[
+  "contact_id",
+  "body"
+]
  2. First observed

TDQS

D1.8/5.0
Behavior1/5

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

The description says 'View a contact by ID', implying a read, while annotations declare readOnlyHint=false and destructiveHint=true. This directly contradicts the structured safety signal. The one useful addition is the master API key requirement, but the contradiction dominates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The functional description is a single terse sentence that mischaracterizes the tool, and it is padded with a multi-line pricing boilerplate block that is irrelevant to selecting or invoking the tool. The valuable content (auth requirement) is buried after the core claim.

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 destructive PATCH tool with a nested update payload and a required body, the description never explains that it mutates a contact, what fields are updatable, or that `label_names` overwrites existing lists. An output schema exists so return values need not be explained, but the mutation semantics are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% and the tool has a nested `body` object with a required but undocumented top-level shape. The description contributes nothing about `contact_id` or the update payload, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says only 'View a contact by ID', but the tool is a PATCH endpoint whose required `body` object contains update fields (email, title, name, labels, etc.) and whose title is 'Update or View Contact'. The description captures the read half and omits the mutation half, which is the primary operation, making it misleading rather than merely vague.

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?

No guidance on when to use this tool versus the obvious read sibling `get_apollo_contacts_contact_id`, or versus the bulk update tools like `post_apollo_contacts_bulk_update`. The only condition stated is 'Requires a master API key', which is an auth note, not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AIsa Sales toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources