Skip to main content
Glama

The Marketing Vault

Get customer profile (ICP)

get_customer_profile
Read-onlyIdempotent

Returns the saved ideal customer profile (ICP), offer details and brand voice for one of the user's businesses. Defaults to the user's default business.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_customer_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_profile_idNoBusiness profile id from list_businesses. Omitted means the default business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no explanation. The description adds real value beyond that by disclosing which data sections are returned and that the default business is used when no id is supplied, though it is silent on what happens when no ICP has been saved yet.

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?

Two short sentences with no filler; the resource and payload are front-loaded and the fallback behavior follows. Nothing could be cut without losing information.

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?

For a single-optional-parameter read tool with full annotation coverage and no output schema, the description covers purpose, scope, and defaulting adequately. The only missing piece an agent might want is the empty/unconfigured-profile case, which is a minor gap at this complexity level.

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% and the single parameter already documents itself as 'Business profile id from list_businesses. Omitted means the default business.' The description merely restates the default behavior, adding no syntax, format, or sourcing detail beyond the schema.

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 names a specific verb ('Returns') and resource, and enumerates the payload (ideal customer profile, offer details, brand voice) rather than restating the title. It does not distinguish itself from siblings such as update_brand_voice or update_business_facts, but the read-only 'get' framing makes the intent unambiguous.

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?

Usage is implied by 'saved ideal customer profile ... for one of the user's businesses' and the defaulting behavior, but there is no explicit when-to-use or when-not-to-use guidance. In particular, it never points at the sibling write tools (update_brand_voice, update_business_facts) as the way to change this data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources