Skip to main content
Glama

capacities_save_weblink

Store web links in 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
descriptionOverwriteNoOptional description for the weblink
mdTextNoText formatted as markdown that will be added to the notes section
spaceIdYesThe UUID of the space to save the weblink to
tagsNoOptional Tags to add to the weblink. Tags need to exactly match your tag names in Capacities, otherwise they will be created.
titleOverwriteNoOptional custom title for the weblink
urlYesThe URL to save

Implementation Reference

  • The asynchronous execute function that implements the core logic of the 'capacities_save_weblink' tool. It constructs a request body from the input arguments and makes a POST request to the '/save-weblink' API endpoint using makeApiRequest, handling success and error responses.
    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 defining the input parameters for the tool, including required spaceId and url, and optional fields like titleOverwrite, descriptionOverwrite, tags, and mdText with descriptions and validations.
    	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:27-27 (registration)
    Registers the saveWeblinkTool (which has name 'capacities_save_weblink') with the FastMCP server instance.
    server.addTool(saveWeblinkTool);
Behavior3/5

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

Annotations indicate readOnlyHint=false (mutation) and openWorldHint=true (supports flexible inputs), which the description aligns with by describing a save operation. It adds context about tag creation if names don't match, but doesn't disclose other behavioral traits like error handling, rate limits, or authentication needs beyond what annotations provide.

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 and lists optional features. Every word contributes to understanding without redundancy or unnecessary elaboration.

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?

For a mutation tool with no output schema and rich annotations, the description adequately covers the basic operation but lacks details on return values, error conditions, or integration with sibling tools. It's minimally viable given the context but has clear gaps in completeness.

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 parameters are fully documented in the schema. The description mentions optional title and tags, which map to titleOverwrite and tags parameters, but adds no additional meaning beyond what the schema already provides (e.g., no usage examples or edge cases).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Save a web link') and target resource ('to a Capacities space'), specifying optional features (title and tags). It distinguishes from siblings like capacities_get_space_info (read-only info) and capacities_save_to_daily_note (different target), but doesn't explicitly differentiate from capacities_search (search vs. save).

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 for saving web links with metadata to a space, but provides no explicit guidance on when to use this tool versus alternatives like capacities_save_to_daily_note (for daily notes) or capacities_search (for finding content). No exclusions or prerequisites are mentioned.

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

Related 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/jem-computer/capacities-mcp'

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