Skip to main content
Glama

Linkedin_ads

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Li List Ad Accounts

li_list_ad_accounts
Read-onlyIdempotent

Check which LinkedIn ad accounts you can access. Returns account IDs, names, and status to identify which account to use for campaigns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoMax results (default 10)
startNoPagination offset (default 0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if connection not found
pagingNoPagination metadata
messageNoError message with guidance
elementsNoList of ad accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "elements": {
+      "description": "List of ad accounts",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Account ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Account name",
+            "type": "string"
+          },
+          "status": {
+            "description": "Account status",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "Error code if connection not found",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message with guidance",
+      "type": "string"
+    },
+    "paging": {
+      "description": "Pagination metadata",
+      "properties": {
+        "count": {
+          "description": "Number of results returned",
+          "type": "number"
+        },
+        "start": {
+          "description": "Pagination start offset",
+          "type": "number"
+        },
+        "total": {
+          "description": "Total available results",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "count": 10,
+    "start": 0
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false. The description adds that it returns account IDs, names, and status, and its purpose for campaign identification. There is no contradiction, and the description adds useful behavioral context beyond 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.

Conciseness5/5

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

Two sentences with no wasted words. The purpose and return values are front-loaded, making it efficient and easy to parse.

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?

Given the output schema exists, the description adequately covers the purpose, returned fields, and use case. Combined with annotations, it provides complete context for a listing tool.

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?

Input schema coverage is 100% with clear descriptions for count and start. The description does not add any new parameter-specific meaning beyond the schema. Baseline 3 is appropriate as the schema already documents the parameters well.

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 clearly states the verb 'Check' and specifies the resource 'LinkedIn ad accounts you can access.' It lists the returned fields (IDs, names, status) and the use case (identify which account to use for campaigns), distinguishing it from sibling tools like li_get_campaign and li_list_campaigns.

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?

The description implies usage when you need to know accessible ad accounts before campaign work. However, it does not explicitly state when not to use it or mention alternatives, though sibling tools are campaign-specific and less likely to overlap.

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

All Linkedin_ads toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources