Skip to main content
Glama
Im-Hal-9K

Capacities-MCP-Plus

capacities_save_weblink

Save web links to a Capacities space with custom titles, descriptions, tags, and markdown notes for organized knowledge management.

Instructions

Save a web link to a Capacities space with optional title and tags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceIdYesThe UUID of the space to save the weblink to
urlYesThe URL to save
titleOverwriteNoOptional custom title for the weblink
descriptionOverwriteNoOptional description for the weblink
tagsNoOptional Tags to add to the weblink. Tags need to exactly match your tag names in Capacities, otherwise they will be created.
mdTextNoText formatted as markdown that will be added to the notes section

Implementation Reference

  • The execute function implementing the tool logic: constructs request body from args and POSTs to /save-weblink via makeApiRequest, handles response or error.
    execute: async (args: {
    	spaceId: string;
    	url: string;
    	titleOverwrite?: string;
    	descriptionOverwrite?: string;
    	tags?: string[];
    	mdText?: string;
    }) => {
    	try {
    		const requestBody = {
    			spaceId: args.spaceId,
    			url: args.url,
    			...(args.titleOverwrite && { titleOverwrite: args.titleOverwrite }),
    			...(args.descriptionOverwrite && {
    				descriptionOverwrite: args.descriptionOverwrite,
    			}),
    			...(args.tags && { tags: args.tags }),
    			...(args.mdText && { mdText: args.mdText }),
    		};
    
    		const response = await makeApiRequest("/save-weblink", {
    			method: "POST",
    			body: JSON.stringify(requestBody),
    		});
    
    		const responseText = await response.text();
    		if (!responseText.trim()) {
    			return "Success: Weblink saved (no response data)";
    		}
    
    		try {
    			const data = JSON.parse(responseText);
    			return JSON.stringify(data, null, 2);
    		} catch (parseError) {
    			return `Success: Weblink saved. Response: ${responseText}`;
    		}
    	} catch (error) {
    		throw new Error(
    			`Failed to save weblink: ${error instanceof Error ? error.message : String(error)}`,
    		);
    	}
  • Zod schema for input parameters: spaceId (uuid), url, optional titleOverwrite, descriptionOverwrite, tags array, mdText.
    parameters: z.object({
    	spaceId: z
    		.string()
    		.uuid()
    		.describe("The UUID of the space to save the weblink to"),
    	url: z.string().url().describe("The URL to save"),
    	titleOverwrite: z
    		.string()
    		.max(500)
    		.optional()
    		.describe("Optional custom title for the weblink"),
    	descriptionOverwrite: z
    		.string()
    		.max(500)
    		.optional()
    		.describe("Optional description for the weblink"),
    	tags: z
    		.array(z.string())
    		.max(30)
    		.optional()
    		.describe(
    			"Optional Tags to add to the weblink. Tags need to exactly match your tag names in Capacities, otherwise they will be created.",
    		),
    	mdText: z
    		.string()
    		.max(200000)
    		.optional()
    		.describe(
    			"Text formatted as markdown that will be added to the notes section",
    		),
    }),
  • src/server.ts:30-30 (registration)
    Registers the capacities_save_weblink tool with the FastMCP server.
    server.addTool(saveWeblinkTool);
Behavior4/5

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

Annotations indicate readOnlyHint=false (write operation) and openWorldHint=true (supports flexible inputs), which the description aligns with by describing a save action. The description adds value by specifying that tags must match existing tag names or will be created, providing behavioral context beyond annotations. However, it doesn't mention rate limits, authentication needs, or error handling.

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 a single, efficient sentence that front-loads the core purpose ('Save a web link to a Capacities space') and includes key optional features. There is no wasted verbiage, and every word contributes to understanding the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (6 parameters, write operation) and lack of output schema, the description is adequate but has gaps. It covers the basic action and optional features, but doesn't explain return values, error conditions, or dependencies on other tools like capacities_list_spaces for space selection. With annotations providing some context, it's minimally viable but not fully comprehensive.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal semantics by mentioning 'optional title and tags,' which correspond to titleOverwrite and tags parameters, but doesn't provide additional meaning beyond what the schema offers. This meets the baseline for high schema coverage.

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 specific action ('save a web link') and resource ('to a Capacities space'), distinguishing it from siblings like capacities_save_to_daily_note (which saves to daily notes) and capacities_search (which searches). It also mentions optional features (title and tags) that differentiate it further from basic save operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning 'optional title and tags,' suggesting when to use these features, but it doesn't explicitly state when to use this tool versus alternatives like capacities_save_to_daily_note or capacities_search. No exclusions or prerequisites are provided, leaving usage context partially inferred.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Im-Hal-9K/Capacities-MCP-Plus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server