Skip to main content
Glama

Linkedin_ads

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Li List Creatives

li_list_creatives
Read-onlyIdempotent

View all ads in a LinkedIn campaign (e.g., campaign ID "501234567"). Returns creative IDs, titles, content, status, and creation dates to compare variations.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if connection not found
pagingNoPagination metadata
messageNoError message with guidance
elementsNoList of creatives (ads)

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 creatives (ads)",
+      "items": {
+        "properties": {
+          "content": {
+            "description": "Creative content or body text",
+            "type": "string"
+          },
+          "createdTime": {
+            "description": "Creation timestamp (milliseconds)",
+            "type": "number"
+          },
+          "id": {
+            "description": "Creative ID",
+            "type": "string"
+          },
+          "status": {
+            "description": "Creative status",
+            "type": "string"
+          },
+          "title": {
+            "description": "Creative title or headline",
+            "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: +[
+  {
+    "campaign_id": "501234567",
+    "count": 10,
+    "start": 0
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds value by listing return fields (IDs, titles, content, status, dates) but does not disclose additional behavioral traits 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: the first states purpose with an example, the second lists return fields. No filler, every word adds value.

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?

With an output schema present, the description does not need to explain return values. It covers the essential information for a list tool, including example usage and expected output fields, and the annotations are comprehensive.

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 the schema already documents each parameter. The description provides an example campaign ID but adds no extra semantic detail beyond the schema.

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 tool's function: 'View all ads in a LinkedIn campaign' with a concrete example. It is specific to creatives within campaigns, distinguishing it from sibling tools like `li_list_campaigns` or `li_campaign_analytics`.

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 provides a clear use case (viewing creatives for comparison) and an example campaign ID. However, it does not explicitly state when not to use it or mention alternatives, though sibling differentiation is implicit.

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