Skip to main content
Glama

Hi, Moose AEO

by com.himoose.mcp
OverviewDiscussionsAdmin

Plan internal links for a page, draft or pasted content

find_internal_links
Read-onlyIdempotent

Plans internal links for one piece of content using the Hi, Moose crawl of the user's own site. Returns two lists: pages this content should link out to, each with the anchor text to use (a phrase quoted from the content when one fits), and existing pages that should add a link pointing to this content, each with the anchor text to use on that page. Pages the content already links to, and pages that already link to it, are left out. The source is required: pass the url of a page, the draftId of a saved draft, or the content as text for a page that is not live yet. If the user gave no source, ask which page, draft or text first. Results depend on the site crawl in Hi, Moose: they cover the pages crawled so far and name the crawl date; pages published since the last crawl are not included. Takes about one minute. Give both lists to the user in full.

Input Schema

NameRequiredDescriptionDefault
urlNoThe URL of the page to plan links for. Works for pages already on the site and for new pages that are live.
titleNoOptional: the title of the content, used when passing content as text. Up to 200 characters.
contentNoThe content as text or markdown, for a page that is not live yet and was not drafted in Hi, Moose. At least a few paragraphs, up to 50000 characters.
draftIdNoThe draftId of a saved draft, from create_draft or list_drafts. Use this for a draft made in Hi, Moose.
projectYesThe Hi, Moose project, by its name as shown by list_projects. The projectId is also accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds substantial behavioral context beyond annotations: crawl-date dependency, exclusion of already-linked pages, approximately one-minute latency, and instructions to return both lists in full.

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?

The description is front-loaded with the tool's purpose and return shape, then proceeds through source requirements, crawl limitations, timing, and output handling. Despite its length, nearly every sentence carries operational value for correct invocation or result presentation.

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?

There is no output schema, but the description compensates by explaining the two returned lists, their anchor-text contents, and what is excluded. Combined with annotations and full schema coverage, an agent has enough information to invoke the tool correctly and present results appropriately.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents the five parameters. The description still adds useful selection semantics by framing url, draftId, and content as alternative required sources and by noting that content is for pages not live yet. This goes beyond the raw field descriptions.

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 begins with a specific verb and resource: 'Plans internal links for one piece of content.' It also distinguishes the exact outputs: outbound link suggestions and inbound link opportunities, each with anchor text, so an agent can tell what this tool uniquely provides.

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 clearly states the source requirement and the three accepted source modes: url, draftId, or content text. It also tells the agent to ask the user for a source when none is given. It does not name alternative sibling tools, but there is no obvious overlapping sibling for this internal-linking task.

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

All Hi, Moose AEO 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