Skip to main content
Glama
Sign In
LinkedIn Ads MCP Server

LinkedIn Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get setup guide

get_setup_guide
Read-onlyIdempotent

Returns step-by-step instructions for connecting a specified AI app to the hosted LinkedIn Ads MCP server, including the exact menu path, command, or config snippet.

Instructions

Get the step-by-step instructions to connect one AI app to the hosted LinkedIn Ads MCP server by AdKit at https://mcp.adkit.so/linkedin-ads. Use this when the user asks how to install, add or connect AdKit in a specific app. Returns Markdown with the exact menu path, command or config snippet. For what the hosted server can do once connected, use list_hosted_tools instead.

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": {
      "app": "<app>"
    },
    "name": "get_setup_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe AI app to connect, exactly as listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/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 description does not need to re-argue safety. It adds genuinely new behavioral detail that annotations cannot carry: the return is Markdown containing the exact menu path, command or config snippet. It stops short of mentioning rate limits or failure modes for an unsupported app name, but the added context is substantial.

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?

Three short sentences, front-loaded with the action and resource, then the trigger, then the return format, then the alternative. Every sentence carries distinct information with no redundancy.

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

Completeness5/5

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

For a single-parameter read-only lookup with no output schema, the definition covers purpose, trigger, return format and the competing sibling. Nothing an agent needs to decide to call it or to interpret the response is missing.

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 'app' parameter has an exhaustive enum with a description, so the schema provides the meaning. The phrase 'one AI app' in the description reinforces that exactly one app is accepted per call, but goes little beyond the schema. Baseline 3 applies.

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?

The description uses a specific verb and resource: 'Get the step-by-step instructions to connect one AI app to the hosted LinkedIn Ads MCP server by AdKit'. It names the server and its URL, so scope and identity are unambiguous, and it distinguishes itself from the sibling that describes server capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the triggering condition explicitly ('Use this when the user asks how to install, add or connect AdKit in a specific app') and names the alternative for a different need ('For what the hosted server can do once connected, use list_hosted_tools instead'), giving both when-to-use and when-to-use-something-else.

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

Deploy Server

Other Tools