Skip to main content
Glama
hackle-io

hackle-mcp

Official
by hackle-io

remote-config-update-user-identifier-criteria

Modify user identifier criteria in remote configurations to refine targeting across production and development environments using Hackle's $deviceId, $userId, or custom criteria.

Instructions

Updates remote config's user identifier criteria. The change will be applied to both production and development environment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
remoteConfigIdYesRemote config's id.

Implementation Reference

  • The asynchronous handler function that executes the tool logic by sending a PATCH request to update the remote config's user identifier criteria via WebClient.
    async ({ body, remoteConfigId }) => {
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await WebClient.patch(`/api/v1/remote-configs/${remoteConfigId}/identifierType`, body)),
          },
        ],
      };
    },
  • Zod schema defining the input parameters: remoteConfigId (number) and body containing userIdentifierCriteria (string).
    {
      remoteConfigId: z.number().positive().describe("Remote config's id."),
      body: z.object({
        userIdentifierCriteria: z
          .string()
          .describe(
            'User identifier criteria for targeting. You can use criteria provided by Hackle($deviceId, $userId) or your own criteria created at Hackle dashboard website.',
          ),
      }),
    },
  • src/index.ts:489-511 (registration)
    Registration of the 'remote-config-update-user-identifier-criteria' tool using server.tool(), including name, description, schema, and inline handler.
      'remote-config-update-user-identifier-criteria',
      "Updates remote config's user identifier criteria. The change will be applied to both production and development environment.",
      {
        remoteConfigId: z.number().positive().describe("Remote config's id."),
        body: z.object({
          userIdentifierCriteria: z
            .string()
            .describe(
              'User identifier criteria for targeting. You can use criteria provided by Hackle($deviceId, $userId) or your own criteria created at Hackle dashboard website.',
            ),
        }),
      },
      async ({ body, remoteConfigId }) => {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(await WebClient.patch(`/api/v1/remote-configs/${remoteConfigId}/identifierType`, body)),
            },
          ],
        };
      },
    );
Behavior2/5

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

With no annotations, the description carries full burden. It discloses that the update applies to both production and development environments, which is useful behavioral context. However, it lacks critical details like permission requirements, whether the change is reversible, rate limits, or error handling for a mutation tool.

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 a single, efficient sentence that directly states the action and scope. It's appropriately sized without unnecessary elaboration, though it could be slightly more structured by separating purpose from behavioral details.

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, no output schema, and incomplete parameter documentation (50% coverage), the description is insufficient. It lacks details on return values, error conditions, side effects, and doesn't fully compensate for the missing structured information, leaving significant gaps for an AI agent.

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 50% (one of two parameters has a description). The description adds no additional parameter semantics beyond what's in the schema. It doesn't explain the structure of 'body' or provide examples for 'userIdentifierCriteria', leaving gaps in understanding the two required parameters.

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 verb ('Updates') and resource ('remote config's user identifier criteria'), making the purpose understandable. It distinguishes from siblings like 'remote-config-update' by specifying the exact aspect being updated, though it doesn't explicitly contrast with all alternatives.

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?

No guidance is provided on when to use this tool versus alternatives like 'remote-config-update' or 'remote-config-update-description'. The description mentions the change applies to both environments but doesn't specify prerequisites, constraints, or appropriate contexts for usage.

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/hackle-io/hackle-mcp'

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