Skip to main content
Glama
LinkedIn Ads MCP Server

LinkedIn Ads MCP Server

by get-mcp-ads

linkedin get entity

linkedin_get_entity
Read-onlyIdempotent

Read a campaign group, campaign, or creative and verify account ownership before accessing LinkedIn Ads entity data.

Instructions

Read one campaign group, campaign or creative and verify account ownership.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "adAccountId": "<adAccountId>",
      "kind": "<kind>",
      "entityId": "<entityId>"
    },
    "name": "linkedin_get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesNative resource type to read or modify.
entityIdYesNative numeric ID or sponsoredCreative URN; account ownership is verified.
adAccountIdYesSelected LinkedIn advertising account, numeric ID. It must be listed in LINKEDIN_ADS_ACCOUNT_IDS.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal tool result: parsed JSON when the text is JSON, otherwise the text. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description contributes the ownership-verification detail, which tells the agent a permission check is part of the call. It adds nothing about failure behavior when ownership fails or about openWorld-related variability, so it is a modest increment over the annotations.

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

Conciseness4/5

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

A single short sentence that front-loads the verb and the resource scope with zero filler. It is efficient, though slightly too terse to carry usage routing or behavioral nuance.

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?

The tool is a simple three-parameter read with 100% schema coverage, full annotations, and an output schema that covers return values. Given that, the description is adequate: it names the entity kinds and the ownership check. Minor gaps remain around choosing this over sibling list/get 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?

Schema description coverage is 100%, and the schema already documents the kind enum, the entityId pattern including the sponsoredCreative URN form, and the account ID constraint. The description only restates the ownership verification that the entityId schema description also mentions, so it adds no semantic value beyond structured fields.

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 states a specific verb and resource set (read one campaign group, campaign, or creative), which is clearly distinct from the plural list siblings such as linkedin_get_campaign_groups and linkedin_get_campaigns. It stops short of naming those siblings as alternatives, so differentiation is implied by the singular noun rather than stated.

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 phrase 'read one' implies this is the single-entity fetch path and that the list tools cover bulk retrieval, and 'verify account ownership' hints at a post-lookup access check. However, there is no explicit when-to-use versus the list tools, no guidance on choosing between it and linkedin_get_account_details, and no preconditions spelled out beyond what the schema already encodes.

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