Skip to main content
Glama
Sign In

MentionAgent

by ai.mentionagent
OverviewDiscussionsAdmin

Set the page outreach links to

set_link_target
DestructiveIdempotent

Choose which page on this site outreach asks for links to, and optionally the anchor phrases for it. 'page' is a path on the site ('/pricing') or a full URL on the same site; an empty string goes back to the homepage. The page is fetched once and a page that errors is refused. 'phrases' is up to 3 phrases of up to 3 words; omit it to keep the current ones, pass [] to clear them. 'more_pages' sets up to 4 EXTRA pages beside the main one, each { page, phrases }; it replaces the whole list, [] clears it. With more than one page, each reply thread asks for one page and keeps it: a site whose post is clearly about one page gets that page, the rest take turns. Read get_campaign first. Sends nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>"
    },
    "name": "set_link_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPath or same-site URL. Empty string for the homepage.
phrasesNoAnchor phrases for the page.
more_pagesNoExtra pages beside the main one. Replaces the list; [] clears it.
workspaceIdYesWhich site to act on. Call get_status with no arguments to list them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / more_pages
      Added value: +{
+  "description": "Extra pages beside the main one. Replaces the list; [] clears it.",
+  "items": {
+    "properties": {
+      "page": {
+        "description": "Path or same-site URL of the page.",
+        "type": "string"
+      },
+      "phrases": {
+        "description": "Up to 3 anchor phrases of up to 3 words.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "page"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Well beyond the annotations: the page is fetched once and an erroring page is refused, phrases are capped at 3 phrases of 3 words, more_pages replaces the entire list and [] clears it, and multi-page setups are distributed one page per reply thread. It also clarifies the operation sends nothing, which sharpens the destructiveHint=true signal.

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?

Front-loaded with the purpose, then per-parameter rules, then the thread-distribution behavior. Dense but each sentence carries information; the multi-page thread explanation is long but not padding.

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?

For a destructive, idempotent mutation tool with no output schema and no return payload, the description covers fetch/validation failure, list-replacement semantics, and the absence of any send side effect. An agent can invoke it correctly without further inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description still adds meaning the schema lacks: path-vs-full-URL acceptance, empty string meaning homepage, the 3-phrase/3-word limits, and the critical omit-vs-[] distinction for both phrases and more_pages. That is genuine added value.

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 opening sentence states a specific verb and object: choosing which page on the site outreach links to, plus optional anchor phrases. It is clearly different from sibling setters like set_email_settings or set_run_settings, and 'Sends nothing' bounds the effect precisely.

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 gives a concrete prerequisite ('Read get_campaign first') and spells out the empty-string, omit, and [] cases, which is real when-to-use guidance. It stops short of naming alternative tools to prefer or explicitly stating when not to use this one.

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

All MentionAgent 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