Skip to main content
Glama
charltonmediagroup

LinkedIn Ads MCP Server

get_account_summary

Retrieve a high-level summary of account performance for a specified date range.

Instructions

Get a high-level summary of account performance over a date range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateRangeYes
Behavior2/5

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

Only states it returns a 'high-level summary', but does not disclose what metrics or data are included, any destructive behavior, permission requirements, or rate limits. No annotations are provided to supplement.

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?

Single sentence of 12 words, perfectly concise with no unnecessary content.

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 no annotations, no output schema, and a single parameter, the description is insufficient. It does not explain what the summary includes (e.g., impressions, clicks), which is important when compared to sibling analytics tools.

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 input schema provides descriptions for startDate and endDate, so schema coverage is high. The description adds no additional parameter meaning beyond the schema, so baseline score of 3.

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

Purpose5/5

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

Clearly states it gets a high-level summary of account performance over a date range. The verb 'Get' and resource 'account summary' are specific, and this purpose distinguishes it from sibling tools that focus on campaigns, creatives, etc.

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 alternatives like get_campaign_analytics or list_campaigns. Does not mention any prerequisites or context.

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/charltonmediagroup/LICampaignsMCP'

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