Skip to main content
Glama
thenavidm

Kit MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update a subscriber's pinned location

update_subscriber_location
Destructive

Update a subscriber's pinned location by providing city, region, country, latitude, longitude, and timezone; requires confirm=true because it may affect delivery or audience membership.

Instructions

Update a subscriber's pinned location. May affect delivery, audience membership, published data or irreversible state. Requires confirm=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoNamed private account from KIT_ACCOUNTS. Defaults to KIT_DEFAULT_ACCOUNT or the first configured account.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete JSON body instead of individual body flags. Supports nullable fields and nested bulk structures. Cannot be combined with body flags or payload_file.
locationNo
payload_fileNoLocal JSON request body file, at most 5 MB. Contents are validated before the API call and are never logged.
subscriber_idYesPositive subscriber id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv3.0.0
    • addedInput schema / $defs
      Added value: +{
+  "location": {
+    "additionalProperties": false,
+    "properties": {
+      "city": {
+        "type": "string"
+      },
+      "country_code": {
+        "type": "string"
+      },
+      "latitude": {
+        "format": "float",
+        "type": "number"
+      },
+      "longitude": {
+        "format": "float",
+        "type": "number"
+      },
+      "state_province": {
+        "type": "string"
+      },
+      "timezone": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "city",
+      "state_province",
+      "country_code",
+      "latitude",
+      "longitude",
+      "timezone"
+    ],
+    "type": "object"
+  }
+}
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for audience/delivery changes, publishing, destructive operations and signing-secret changes. Use only for an action requested by the user."New value: +"Set true only when the user asked for exactly this action."
    • addedInput schema / properties / location / $ref
      Added value: +"#/$defs/location"
    • removedInput schema / properties / location / additionalProperties
      Removed value: -false
    • removedInput schema / properties / location / properties
      Removed value: -{
-  "city": {
-    "type": "string"
-  },
-  "country_code": {
-    "type": "string"
-  },
-  "latitude": {
-    "format": "float",
-    "type": "number"
-  },
-  "longitude": {
-    "format": "float",
-    "type": "number"
-  },
-  "state_province": {
-    "type": "string"
-  },
-  "timezone": {
-    "type": "string"
-  }
-}
    • removedInput schema / properties / location / required
      Removed value: -[
-  "city",
-  "state_province",
-  "country_code",
-  "latitude",
-  "longitude",
-  "timezone"
-]
    • removedInput schema / properties / location / type
      Removed value: -"object"
    • addedInput schema / properties / payload / properties / location / $ref
      Added value: +"#/$defs/location"
    • removedInput schema / properties / payload / properties / location / additionalProperties
      Removed value: -false
    • removedInput schema / properties / payload / properties / location / properties
      Removed value: -{
-  "city": {
-    "type": "string"
-  },
-  "country_code": {
-    "type": "string"
-  },
-  "latitude": {
-    "format": "float",
-    "type": "number"
-  },
-  "longitude": {
-    "format": "float",
-    "type": "number"
-  },
-  "state_province": {
-    "type": "string"
-  },
-  "timezone": {
-    "type": "string"
-  }
-}
    • removedInput schema / properties / payload / properties / location / required
      Removed value: -[
-  "city",
-  "state_province",
-  "country_code",
-  "latitude",
-  "longitude",
-  "timezone"
-]
    • removedInput schema / properties / payload / properties / location / type
      Removed value: -"object"
  2. First observedv2.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description adds real value beyond them by naming downstream effects ('delivery, audience membership, published data') and 'irreversible state,' plus the confirm gate. It stops short of describing auth/account requirements or what exactly is overwritten.

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?

Three short sentences with no filler, and the safety-critical confirmation requirement is stated up front. Every sentence carries distinct information.

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

Completeness4/5

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

For a destructive, non-idempotent mutation with a nested body, the description covers the confirmation gate and the affected-state risk, and there is no output schema to explain. It would be stronger if it clarified how to choose among the payload, location, and payload_file input forms.

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 83%, so the schema largely documents the parameters itself, including the nested location object with six required fields. The description only adds the confirm requirement, leaving payload/payload_file/account alternatives to the schema, so the baseline 3 applies.

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?

States a specific verb ('Update') and resource ('a subscriber's pinned location'), which is precise enough to distinguish it from most siblings. It does not explicitly contrast with the nearby pin_subscriber_location and delete_subscriber_location tools, which is the only missing differentiation.

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?

States a hard precondition ('Requires confirm=true') and the confirm parameter reinforces it with 'Set true only when the user asked for exactly this action.' However, it gives no guidance on when to update versus pin or delete a location, which is the likely confusion point among siblings.

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

Deploy Server

Other Tools