DocsSigns of generated text

MCP toolsInside a siteUpdated

Signs of generated text

mttr_tellsAny key

What does mttr_tells do?

Signs of generated text on a site’s pages: hidden characters that can carry a watermark or hidden instructions, chat and markdown left in, placeholders never filled in, stock phrasing, and heavy use of dashes. Any key may make this call, on any public site.

When to use it

  • Pages were drafted with an assistant and you want them checked.
  • You want hidden characters out before publishing.

What you ask

You say“Check example.com for signs of generated text.”

Your assistant calls
mttr_tells({
  site: "example.com"
})
ArgumentTypeNeededWhat it is
siteTextYesThe site, as a domain such as example.com.
showOne of theseNostrong (the default): pages with hidden or left-in text; all: any sign.strongall
limitNumberNoHow many to return.
offsetNumberNoHow many to skip, for the next part of a long list.

What comes back

  • Each sign with its pages, strong signs first.
  • Any message hidden in tag characters, spelled out.
  • A sign is not proof.
What it answersSample
SignPagesStrength
Hidden characters3Strong
Placeholder left in1Strong
Stock phrasing7Weak

Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.

Over HTTP

It is GET /api/v1/sites/{site}/tells, with your key as a bearer token:

HTTP
curl "https://clickd.com/api/v1/sites/example.com/tells" \
  -H "Authorization: Bearer $CLICKD_KEY"

When it fails

WhenStatusWhat to do
Your assistant has no key and has made 60 calls this hourisError over MCPWait the minutes it says, or sign up with mttr_signup and connect again with the key it gives.
clickd has no public report of the site yet404Ask for a read with mttr_rescan, then watch it with mttr_job.

Every error’s wording is in the API reference.

The call in full, with its HTTP address, each argument’s type, who may make it and the call in four languages, is mttr_tells in the API reference.

Goes with

Sources

This page as Markdown