Influence

Search Farcaster channels

wrapcastChannelSearch

Read-onlyIdempotent

Find a destination channel using at least two characters. Requires an owned active account and current provider availability. Follow nextCursor until done, keeping the same connection and search fields.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	Farcaster channel search text, at least two characters
`cursor`	No	nextCursor from the previous page of this exact tool and input
`connectionId`	Yes	Owned connectionId returned by accountList

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedOutput schema / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "ok": {
-        "const": true,
-        "type": "boolean"
-      },
-      "output": {
-        "additionalProperties": false,
-        "properties": {
-          "output": {
-            "additionalProperties": false,
-            "properties": {
-              "done": {
-                "$ref": "#/$defs/__schema0"
-              },
-              "items": {
-                "$ref": "#/$defs/__schema1"
-              },
-              "nextCursor": {
-                "$ref": "#/$defs/__schema3"
-              }
-            },
-            "required": [
-              "done",
-              "items"
-            ],
-            "type": "object"
-          }
-        },
-        "required": [
-          "output"
-        ],
-        "type": "object"
-      },
-      "toolName": {
-        "const": "wrapcastChannelSearch",
-        "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": "wrapcastChannelSearch",
-        "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": {
+              "done": {
+                "$ref": "#/$defs/__schema0"
+              },
+              "items": {
+                "$ref": "#/$defs/__schema1"
+              },
+              "nextCursor": {
+                "$ref": "#/$defs/__schema3"
+              }
+            },
+            "required": [
+              "done",
+              "items"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "output"
+        ],
+        "type": "object"
+      },
+      "toolName": {
+        "const": "wrapcastChannelSearch",
+        "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": "wrapcastChannelSearch",
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "ok",
+      "toolName"
+    ],
+    "type": "object"
+  }
+]

First observedOct 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing an authorization requirement ('owned active account'), an availability dependency, and the pagination discipline of keeping the same connection and search fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Three compact sentences with the purpose front-loaded ahead of prerequisites and pagination guidance. No filler, though it is fairly dense and could group the caveats more cleanly.

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 return values need not be described, and annotations carry the safety profile. The description covers prerequisites and pagination, leaving only the sibling-selection decision unaddressed, which is minor for a niche Farcaster 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 are already documented in the schema (including the two-character minimum and the cursor provenance). The description only reinforces the length rule and cursor reuse, adding no syntax or format detail the schema lacks; baseline 3 is appropriate.

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 gives a specific verb+resource ('Find a destination channel') and names the Farcaster channel domain via the title, so an agent knows this searches channels. It does not explicitly distinguish itself from other platform channel/search siblings (discordChannelList, slackChannelList, lemmyCommunitySearch), leaving that inference to the agent.

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?

It states the search precondition (at least two characters), a hard prerequisite (owned active account), and an environmental caveat (current provider availability). It also prescribes the pagination workflow ('Follow nextCursor until done'), but names no alternative tool or when-not-to-use condition.

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

All Influence tools Inspect

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

Need Help?