docs.usepylon.com
Introduction
First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com
Answer 2 · Act 0 · Transact 1 · Score: Not yet scored
Tool inspector
sendFeedback
Report an issue in the documentation of Pylon so the team can fix it. Use it whenever, while helping a user, you come across content that is outdated, contradictory, missing information, or otherwise unhelpful. Also use it when the user themselves reports a problem with the docs, even if you could not verify it yourself. If it's your own observation, do a quick sanity check that the issue is real before reporting — no need to exhaustively re-read the page. Send one call per distinct issue and do not report the same issue twice in a conversation. Do not use this tool to confirm that a page is accurate; it is for reporting problems only.
Page: /pylon-docs
Input schema
| Property | Type | Required | Description |
|---|---|---|---|
content |
string | yes | Explain the issue in full, as if writing to a documentation maintainer who never saw this conversation. Describe what is wrong, where on the page it appears (quote the exact sentence or section title when possible), what the user was trying to do, and, when relevant, what the correct or expected information should be. Write a few clear, specific sentences in English. Never include personal or confidential information from the conversation. Up to 2048 characters. |
pageUrl |
string | yes | The full URL of the page the issue is about (e.g. https://docs.usepylon.com/pylon-docs//getting-started), so the finding is linked to the exact page. |
goal |
string | no | The broader end goal you were ultimately trying to accomplish (as/on behalf of the user) when you hit this issue. Gives the team the context you were working towards. Optional. |
Raw JSON schema
{
"type": "object",
"properties": {
"content": {
"type": "string",
"minLength": 1,
"maxLength": 2048,
"description": "Explain the issue in full, as if writing to a documentation maintainer who never saw this conversation. Describe what is wrong, where on the page it appears (quote the exact sentence or section title when possible), what the user was trying to do, and, when relevant, what the correct or expected information should be. Write a few clear, specific sentences in English. Never include personal or confidential information from the conversation. Up to 2048 characters."
},
"pageUrl": {
"type": "string",
"description": "The full URL of the page the issue is about (e.g. https://docs.usepylon.com/pylon-docs//getting-started), so the finding is linked to the exact page."
},
"goal": {
"type": "string",
"maxLength": 1024,
"description": "The broader end goal you were ultimately trying to accomplish (as/on behalf of the user) when you hit this issue. Gives the team the context you were working towards. Optional."
}
},
"required": [
"content",
"pageUrl"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
Similar websites
econsor.de
German digital agency building portals, e-commerce sites and online marketing, combining strategy, design and AI to grow clients' visibility and customer base.
inkframe-eta.vercel.app
Browser-native Elah video editor for 9:16 and 16:9 exports
agentdesk-demo.vercel.app
Meridian Ops
eworker.ca
E-Worker is business infrastructure powered by AI, with focused apps and connected business work.