Skip to main content
Glama
FromSmall2Big

Apollo.io MCP Server

get_account_by_id

Retrieve detailed account information from Apollo.io using a specific account ID to access contact data, custom fields, and associated personas for sales and marketing activities.

Instructions

Retrieve detailed information for a specific account by ID.

This tool fetches comprehensive account data including contact information, custom fields, and associated personas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'get_account_by_id' tool. It is decorated with @mcp.tool() which registers it with the FastMCP server. The function retrieves account details from the Apollo.io API by making a GET request to /v1/accounts/{account_id} using the shared ApolloAPIClient instance.
    @mcp.tool()
    async def get_account_by_id(account_id: str) -> Dict[str, Any]:
        """
        Retrieve detailed information for a specific account by ID.
        
        This tool fetches comprehensive account data including contact information,
        custom fields, and associated personas.
        """
        endpoint = f"/v1/accounts/{account_id}"
        
        try:
            result = await apollo_client.make_request("GET", endpoint)
            return result
        except httpx.HTTPStatusError as e:
            return {"error": f"API request failed: {e.response.status_code} {e.response.text}"}
        except Exception as e:
            return {"error": f"Request failed: {str(e)}"}
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions fetching 'comprehensive account data' but doesn't disclose behavioral traits such as whether this is a read-only operation, authentication requirements, rate limits, error handling, or data freshness. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves beyond basic functionality.

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 appropriately sized with two sentences: the first states the core purpose, and the second elaborates on the data included. It's front-loaded with the main action and resource, with no wasted words. Every sentence adds value by clarifying scope and content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (single parameter), lack of annotations, and presence of an output schema (which handles return values), the description is reasonably complete. It covers the purpose, parameter semantics, and data scope. However, it could improve by addressing behavioral aspects like read-only nature or error cases, which are missing despite the output schema.

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

Parameters4/5

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

The description adds meaning by specifying that the tool retrieves data 'by ID', which clarifies the purpose of the 'account_id' parameter beyond what the schema provides (schema coverage is 0%). Since there's only one parameter and the description explains its role, it compensates well for the lack of schema descriptions, though it doesn't detail format constraints like ID structure.

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 verb ('Retrieve', 'fetches') and resource ('detailed information for a specific account by ID'), making the purpose evident. It distinguishes from siblings like 'search_accounts' by specifying retrieval by ID rather than search criteria. However, it doesn't explicitly contrast with 'get_email_accounts' or 'enrich_organization', leaving some sibling differentiation incomplete.

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 when you need comprehensive account data for a known account ID, but it doesn't explicitly state when to use this versus alternatives like 'search_accounts' (for unknown IDs) or 'enrich_organization' (for organization-level data). No exclusions or prerequisites are mentioned, leaving usage context partially implied rather than fully guided.

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/FromSmall2Big/Apollo-MCP'

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