Skip to main content
Glama

Linkedin_ads

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Li List Campaigns

li_list_campaigns
Read-onlyIdempotent

Get all campaigns in a LinkedIn ad account (e.g., account ID "501234567"). Returns campaign IDs, names, budgets, status, and date ranges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoMax results (default 10)
startNoPagination offset (default 0)
account_idYesSponsored account ID (numeric, e.g., "508127070")

Output Schema

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

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 campaigns",
+      "items": {
+        "properties": {
+          "budget": {
+            "description": "Campaign budget details",
+            "properties": {
+              "amount": {
+                "description": "Budget amount",
+                "type": "number"
+              },
+              "currencyCode": {
+                "description": "Currency code (e.g., USD)",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "endDate": {
+            "description": "Campaign end date",
+            "properties": {
+              "day": {
+                "type": "number"
+              },
+              "month": {
+                "type": "number"
+              },
+              "year": {
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "id": {
+            "description": "Campaign ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Campaign name",
+            "type": "string"
+          },
+          "startDate": {
+            "description": "Campaign start date",
+            "properties": {
+              "day": {
+                "type": "number"
+              },
+              "month": {
+                "type": "number"
+              },
+              "year": {
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "status": {
+            "description": "Campaign 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: +[
+  {
+    "account_id": "508127070",
+    "count": 10,
+    "start": 0
+  }
+]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds return field details (IDs, names, budgets, etc.) but does not disclose additional behavioral traits beyond what annotations provide. No contradiction found.

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 concise sentences with the purpose upfront. No unnecessary words. Every sentence adds value: first states action, second lists outputs.

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?

The tool has an output schema, so return values need no further explanation. Parameters are fully described in schema with 100% coverage. The description mentions pagination via count and start implicitly, and the output fields. Complete 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?

Schema description coverage is 100%, so baseline is 3. The description adds an example account ID ('501234567') but does not provide additional semantic meaning for parameters beyond the schema. The mention of return fields is about output, not input parameters.

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 'Get all campaigns in a LinkedIn ad account' with specific verb and resource. It also lists the return fields (IDs, names, budgets, status, date ranges). Distinguishes from siblings like li_get_campaign (single campaign) and li_campaign_analytics (analytics).

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 description implies usage for listing campaigns but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or exclusions, relying on siblings to imply context.

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