Skip to main content
Glama
mcp-linkedin-ads

mcp-linkedin-ads

by mharnett

linkedin_ads_get_client_context

Retrieves the current client context and health status based on the working directory to confirm which LinkedIn Ads account is active before managing campaigns or analytics.

Instructions

Get the current client context and health status based on working directory. Call this first to confirm which LinkedIn Ads account you're working with.

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": {
      "working_directory": "<working_directory>"
    },
    "name": "linkedin_ads_get_client_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
working_directoryYesThe current working directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It does disclose the key behavioral trait that resolution depends on the working directory and that the tool is intended as a prerequisite first call, which implies a read-only, non-destructive operation. However, it says nothing about what happens when no client is configured for that directory, whether it errors or returns a default, or any auth/permission requirements.

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 waste; the action is stated first and the usage directive second. Every sentence earns its place and nothing is buried.

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

Completeness3/5

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

For a simple one-parameter tool this is mostly adequate, and the forced-first-call guidance covers the main operational need. With no output schema, though, the description should say roughly what 'client context and health status' contain (e.g., account ID, name, token validity) so the agent knows what it will learn before proceeding.

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 coverage is 100% with a single documented parameter, so the baseline is 3. The description adds only that the working directory is the basis for resolving the client context, which is useful linkage but not syntax or format 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 uses a specific verb+resource ('Get the current client context and health status') and adds the resolution mechanism ('based on working directory'). The second sentence clarifies the practical purpose (confirming which LinkedIn Ads account is active), which distinguishes it from the sibling list/performance tools. It stops short of a 5 because 'client context and health status' remains somewhat abstract about what is actually returned.

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

Usage Guidelines4/5

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

Explicit sequencing guidance is given: 'Call this first to confirm which LinkedIn Ads account you're working with.' That tells the agent both when to call it (before other work) and why (to confirm account). No alternative or exclusion is named, but as an entrypoint/bootstrap tool there is little to compare against, so this is close to complete.

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