Skip to main content
Glama

Leadconnector

by io.github.pipeworx-io

Generate llms.txt

generate_llms_txt
Read-onlyIdempotent

Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull URL of the site to summarize, e.g. "https://example.com" or a specific landing page.
max_linksNoMaximum number of link entries to include (default 25, max 50).

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds detail: fetches page, extracts title/description/key links, emits standard markdown format. No contradictions.

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?

The description is front-loaded with purpose and well-structured, but slightly longer than necessary. Every sentence adds value, so minor deduction for wordiness.

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?

Given the simple tool (2 params, no output schema), the description covers input, output format, and use cases. It doesn't mention error handling or rate limits, but annotations handle safety. Adequate for its complexity.

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 coverage is 100% with clear descriptions for both parameters. The description only repeats 'for any URL' and does not add new semantics beyond the schema. Baseline of 3 is appropriate.

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 clearly states the verb ('Generate') and resource ('llms.txt file for any URL'), and distinguishes itself by listing specific use cases. No sibling tool has a similar purpose, so differentiation is not needed.

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 provides explicit context ('so AI crawlers can index the site cleanly') and lists three concrete use cases. It lacks explicit when-not-to-use or alternatives, but the unique function makes this less critical.

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

All Leadconnector toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, such as ask_pipeworx and ask_pipeworx_grounded, or bet_research and polymarket_edges. The mix of CRM, data, and betting tools creates confusion about which tool to use for a given task.

Naming Consistency2/5

Tool names are inconsistent, mixing snake_case (ai_visibility_check, ask_pipeworx) with prefixed names (leadconnector_*) and no clear pattern. Some names are vague (forget, remember) while others are specific.

Tool Count2/5

With 32 tools, the set feels overstuffed for a server named 'Leadconnector'. Many tools are unrelated to CRM (e.g., Polymarket, Pipeworx), and the CRM subset is too small to justify the count.

Completeness2/5

For the Leadconnector CRM domain, only basic read operations are provided; missing create, update, delete for contacts, campaigns, and opportunities. The non-CRM tools are comprehensive but don't match the server's name.

Resources