Skip to main content
Glama

Clickup

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.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint=false. The description adds behavioral details: fetching the page, extracting title/description/key links, and emitting standard markdown. It also notes the output is a single text blob. 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 the main purpose and consists of four informative sentences. It is concise without being overly terse, making it efficient for an AI agent to parse.

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?

Given the tool has two parameters, no output schema, and annotations covering safety, the description provides sufficient context: it explains the output format, use cases, and parameter constraints. It is complete for an agent to invoke correctly.

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 description adds value beyond schema by providing examples for the 'url' parameter and specifying default/max for 'max_links'. This improves parameter understanding.

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 tool generates a production-ready llms.txt file for any URL. It specifies the actions (fetches, extracts, emits) and the output format, making the purpose unambiguous. While not explicitly differentiating from siblings, the unique functionality ensures distinctiveness.

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 lists concrete use cases (getting a site indexed, drafting llms.txt, auditing competitors). It provides clear context for when to use the tool. Although it does not mention when not to use or alternatives, the usage guidance is strong.

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

All Clickup 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.6/5.0
Disambiguation3/5

Many tools have distinct purposes, but there is overlap among query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) and among prediction market tools. Detailed descriptions help differentiate, but the large number of tools increases chance of misselection.

Naming Consistency2/5

Naming is highly inconsistent, mixing snake_case and camelCase conventions. ClickUp tools use 'clickup_' prefix while Pipeworx tools have varied patterns (ask_, scan_, validate_, etc.). No unified convention across the set.

Tool Count2/5

35 tools is excessive for a server named 'Clickup', with only 6 ClickUp-specific tools. The remaining 29 are from Pipeworx, which is unrelated. The count is inappropriate for the server's stated purpose.

Completeness2/5

The ClickUp integration is incomplete, missing basic CRUD operations like update and delete tasks. The Pipeworx side is comprehensive but not relevant to the server's name. For a ClickUp server, coverage is poor.

Resources