Skip to main content
Glama
flin-agency

flin-linkedin-ads-mcp

by flin-agency

list_campaigns

List campaigns for a LinkedIn Ads account. Supports filtering, sorting, and pagination.

Instructions

List campaigns for an ad account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNo
searchNo
page_sizeNo
page_tokenNo
sort_orderNo
testNo
ad_account_idNo
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 fails to disclose important behavior such as pagination (page_size, page_token), search, sorting, or result limits. The description is too minimal to inform the agent of side effects or constraints.

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?

While the description is very short (one sentence), it sacrifices necessary information. It is under-specified rather than concisely complete. Important details about parameters and behavior are missing.

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

Completeness1/5

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

With 7 parameters, no output schema, and no annotations, the description is severely incomplete. It does not cover how to use pagination, filtering, sorting, or what the response will contain.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any of the 7 parameters. It does not add meaning beyond the schema. For example, 'fields', 'search', 'page_size' remain opaque.

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 tool lists campaigns for an ad account, which is specific and distinct from sibling tools like get_campaign (individual) and list_campaign_groups (campaign groups). However, it could further differentiate from list_creatives or list_ad_accounts.

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 vs alternatives like get_campaign or list_campaign_groups. The description provides no context for selection.

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/flin-agency/flin-linkedin-ads-mcp'

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