Skip to main content
Glama

Influence

by so.influence
OverviewDiscussionsAdmin

Get Integration Schema

integrationSchema
Read-onlyIdempotent

Returns native platform publishing rules, image and video limits, maximum text length and required settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesStable publishing platform identifier
isPremiumNoDeprecated and ignored; limits come from the selected account
connectionIdNoSelected account connectionId for verified account and native instance limits

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / oneOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "ok": {
-        "const": true,
-        "type": "boolean"
-      },
-      "output": {
-        "additionalProperties": false,
-        "properties": {
-          "output": {
-            "additionalProperties": false,
-            "properties": {
-              "maxLength": {
-                "maximum": 1000000,
-                "minimum": 0,
-                "type": "integer"
-              },
-              "rules": {
-                "maxLength": 8192,
-                "type": "string"
-              },
-              "settings": {
-                "$ref": "#/$defs/__schema0"
-              }
-            },
-            "required": [
-              "maxLength",
-              "rules",
-              "settings"
-            ],
-            "type": "object"
-          }
-        },
-        "required": [
-          "output"
-        ],
-        "type": "object"
-      },
-      "toolName": {
-        "const": "integrationSchema",
-        "type": "string"
-      }
-    },
-    "required": [
-      "ok",
-      "output",
-      "toolName"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "additionalProperties": false,
-        "properties": {
-          "code": {
-            "enum": [
-              "INVALID_INPUT",
-              "FORBIDDEN",
-              "NOT_FOUND",
-              "CONFLICT",
-              "FEATURE_DISABLED",
-              "CONFIRMATION_REQUIRED",
-              "CONFIRMATION_INVALID",
-              "UPSTREAM_FAILED",
-              "NEEDS_REVIEW",
-              "INTERNAL"
-            ],
-            "type": "string"
-          },
-          "message": {
-            "maxLength": 2048,
-            "minLength": 1,
-            "type": "string"
-          },
-          "retryable": {
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "code",
-          "message",
-          "retryable"
-        ],
-        "type": "object"
-      },
-      "ok": {
-        "const": false,
-        "type": "boolean"
-      },
-      "toolName": {
-        "const": "integrationSchema",
-        "type": "string"
-      }
-    },
-    "required": [
-      "error",
-      "ok",
-      "toolName"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "ok": {
+        "const": true,
+        "type": "boolean"
+      },
+      "output": {
+        "additionalProperties": false,
+        "properties": {
+          "output": {
+            "additionalProperties": false,
+            "properties": {
+              "maxLength": {
+                "maximum": 1000000,
+                "minimum": 0,
+                "type": "integer"
+              },
+              "rules": {
+                "maxLength": 8192,
+                "type": "string"
+              },
+              "settings": {
+                "$ref": "#/$defs/__schema0"
+              }
+            },
+            "required": [
+              "maxLength",
+              "rules",
+              "settings"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "output"
+        ],
+        "type": "object"
+      },
+      "toolName": {
+        "const": "integrationSchema",
+        "type": "string"
+      }
+    },
+    "required": [
+      "ok",
+      "output",
+      "toolName"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "additionalProperties": false,
+        "properties": {
+          "code": {
+            "enum": [
+              "AI_SCHEDULING_LIMIT_REACHED",
+              "AI_SCHEDULING_UNAVAILABLE",
+              "INVALID_INPUT",
+              "FORBIDDEN",
+              "NOT_FOUND",
+              "CONFLICT",
+              "FEATURE_DISABLED",
+              "CONFIRMATION_REQUIRED",
+              "CONFIRMATION_INVALID",
+              "UPSTREAM_FAILED",
+              "NEEDS_REVIEW",
+              "INTERNAL"
+            ],
+            "type": "string"
+          },
+          "message": {
+            "maxLength": 2048,
+            "minLength": 1,
+            "type": "string"
+          },
+          "retryable": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "code",
+          "message",
+          "retryable"
+        ],
+        "type": "object"
+      },
+      "ok": {
+        "const": false,
+        "type": "boolean"
+      },
+      "toolName": {
+        "const": "integrationSchema",
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "ok",
+      "toolName"
+    ],
+    "type": "object"
+  }
+]
  2. Changed1 schema field changed
    • changedOutput schema / $defs / __schema0 / anyOf
      Previous value: -[
-  {
-    "maxLength": 8192,
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  },
-  {
-    "items": {
-      "$ref": "#/$defs/__schema0"
-    },
-    "maxItems": 512,
-    "type": "array"
-  },
-  {
-    "additionalProperties": {
-      "$ref": "#/$defs/__schema0"
-    },
-    "propertyNames": {
-      "$ref": "#/$defs/__schema1"
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "maxLength": 8192,
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  },
+  {
+    "items": {
+      "$ref": "#/$defs/__schema0"
+    },
+    "maxItems": 2000,
+    "type": "array"
+  },
+  {
+    "additionalProperties": {
+      "$ref": "#/$defs/__schema0"
+    },
+    "propertyNames": {
+      "$ref": "#/$defs/__schema1"
+    },
+    "type": "object"
+  }
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / platform / description
      Previous value: -"Platform identifier returned by accountList or integrationList"New value: +"Stable publishing platform identifier"
  4. Changed3 schema fields changed
    • changedInput schema / properties / connectionId / description
      Previous value: -"Optional selected account connectionId for verified native instance limits"New value: +"Selected account connectionId for verified account and native instance limits"
    • changedInput schema / properties / isPremium / description
      Previous value: -"Whether premium X limits apply to this integration"New value: +"Deprecated and ignored; limits come from the selected account"
    • changedInput schema / required
      Previous value: -[
-  "isPremium",
-  "platform"
-]New value: +[
+  "platform"
+]
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the nature of the payload (publishing rules, media and text limits, required settings), which helps an agent judge relevance, but says nothing about auth requirements, caching, or freshness of the limits. With annotations carrying the behavioral burden, a 3 is appropriate.

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?

A single sentence that front-loads the verb and then enumerates the payload with no filler or restatement of the name. Every clause carries information an agent can use.

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

Completeness4/5

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

An output schema exists, so the description is not obligated to explain return values, and the schema fully documents parameters and their constraints. What is missing is any routing or timing guidance (when this must be called relative to publishing flows), which is the only material gap for a low-complexity read 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 all three parameters (platform, isPremium, connectionId) are already documented, including the fact that isPremium is deprecated and that limits come from the selected account. The description adds no parameter-level meaning beyond that, which is the baseline expectation when the schema does the heavy lifting.

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 states a specific verb and resource ('Returns native platform publishing rules, image and video limits, maximum text length and required settings'), which is far more informative than the title alone. It does not, however, name or contrast itself with near-neighbours such as redditSubredditRequirementsGet or tiktokCreatorInfoGet, so sibling differentiation is left to inference.

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?

There is no explicit when-to-use statement, but the enumerated return content (limits, required settings) strongly implies the tool is for validating content against platform constraints before composing or publishing. No prerequisites, exclusions, or alternatives are given, so usage remains implied rather than stated.

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

All Influence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources