Skip to main content
Glama

update_link

Modify an existing Dub.co short link by updating its destination URL, domain, or custom slug to maintain accurate redirects.

Instructions

Update an existing short link on dub.co

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkIdYesThe ID of the link to update
urlNoThe new destination URL
domainNoThe new domain for the short link
keyNoThe new slug for the short link

Implementation Reference

  • The handler function that validates input parameters, prepares the update payload using UpdateLinkParams type, makes a PATCH request to /links/{linkId} on the dub.co API, and returns success or error response.
    private async updateLink(args: any): Promise<any> {
      if (!args.linkId) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Link ID is required'
        );
      }
    
      // Prepare update parameters
      const updateParams: UpdateLinkParams = {};
      
      if (args.url) {
        updateParams.url = args.url;
      }
      
      if (args.domain) {
        updateParams.domain = args.domain;
      }
      
      if (args.key) {
        updateParams.key = args.key;
      }
      
      if (Object.keys(updateParams).length === 0) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'At least one parameter to update is required'
        );
      }
      
      try {
        const response = await this.axiosInstance.patch(`/links/${args.linkId}`, updateParams);
        const link = response.data;
        
        return {
          content: [
            {
              type: 'text',
              text: `Link updated: ${link.shortLink}\n\nDestination: ${link.url}\nID: ${link.id}`,
            },
          ],
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          const axiosError = error as AxiosError<ApiErrorResponse>;
          const statusCode = axiosError.response?.status;
          const errorData = axiosError.response?.data;
          const errorMessage = errorData?.error || errorData?.message || axiosError.message;
          
          return {
            content: [
              {
                type: 'text',
                text: `Error updating link: ${statusCode} - ${errorMessage}`,
              },
            ],
            isError: true,
          };
        }
        
        throw error;
      }
    }
  • src/index.ts:130-155 (registration)
    Registration of the 'update_link' tool in the ListToolsRequestSchema handler, including name, description, and input schema defining required linkId and optional update fields.
    {
      name: 'update_link',
      description: 'Update an existing short link on dub.co',
      inputSchema: {
        type: 'object',
        properties: {
          linkId: {
            type: 'string',
            description: 'The ID of the link to update',
          },
          url: {
            type: 'string',
            description: 'The new destination URL',
          },
          domain: {
            type: 'string',
            description: 'The new domain for the short link',
          },
          key: {
            type: 'string',
            description: 'The new slug for the short link',
          },
        },
        required: ['linkId'],
      },
    },
  • TypeScript interface defining the parameters for updating a link, used to type the payload sent to the dub.co API.
    interface UpdateLinkParams {
      url?: string;
      domain?: string;
      key?: string;
      externalId?: string;
      // ... other optional parameters
    }
  • Dispatch case in the CallToolRequestSchema handler that routes 'update_link' calls to the updateLink method.
    case 'update_link':
      return await this.updateLink(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation but doesn't mention what permissions are required, whether changes are reversible, what happens to existing data not mentioned in parameters, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 states exactly what the tool does without any wasted words. It's appropriately sized and front-loaded with the essential information.

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

Completeness2/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 annotations and no output schema, the description is insufficient. It doesn't explain what happens when the update succeeds or fails, what permissions are needed, or how this differs from sibling tools. Given the complexity of updating database records and the lack of structured safety information, more context is needed.

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 all parameters are documented in the schema. The description adds no additional parameter information beyond what the schema provides. According to scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no parameter information in the description.

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 ('Update') and resource ('an existing short link on dub.co'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'upsert_link' which might also update links, leaving some ambiguity about when to choose one over the other.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'upsert_link' or 'create_link'. It mentions 'existing short link' which implies a prerequisite that the link must already exist, but offers no explicit when/when-not instructions or comparison with sibling tools.

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/Gitmaxd/dubco-mcp-server'

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