OpenQR

This connector has been deprecated

This has been replaced by https://glama.ai/mcp/connectors/uk.openqr/qr

update_dynamic_qr

Edit a dynamic QR code: change its destination, label, custom short link (slug), tags or folder. Pass only the fields you want to change. Requires an OpenQR API key.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The dynamic code id.
`pin`	No	Pro: require a 4-digit PIN before the code redirects. Exactly 4 digits. Pass null to remove all protection.
`slug`	No	Custom short-link back-half (oqr.to/<slug>): 3–48 letters, numbers or hyphens.
`tags`	No	Replace the code's tags (max 10).
`label`	No	New label.
`theme`	No	A saved theme id or name to restyle the code with.
`status`	No	Pause the code (it stops resolving — scanners see an inactive page) or reactivate it. Free allows 1 active code; Pro 25.
`password`	No	Pro: require this password before the code redirects (min 4 characters). Pass null to remove all protection.
`folder_id`	No	Move into a folder id, or null to un-file.
`lock_hint`	No	Optional hint shown on the unlock page, e.g. "Ask at the bar". Max 60 characters.
`destination`	No	New http(s) URL.
`pause_until`	No	ISO 8601 timestamp: schedule a pause until then (scanners see the inactive page; the code self-resumes at the deadline). Pass null to clear the schedule. Future timestamps only, active codes only.
`ios_destination`	No	App links: iOS scanners follow this http(s) URL instead of destination (e.g. the App Store page). Pass null to clear. Applies to the plain redirect only.
`android_destination`	No	App links: Android scanners follow this http(s) URL instead of destination (e.g. the Google Play page). Pass null to clear.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

changedInput schema / properties / status / description

Previous value: -"Pause the code (it stops resolving — scanners see an inactive page) or reactivate it. Free plan allows up to 1 active code."New value: +"Pause the code (it stops resolving — scanners see an inactive page) or reactivate it. Free allows 1 active code; Pro 25."

Changed1 schema field changedSep 8, 2026

changedInput schema / properties / status / description

Previous value: -"Pause the code (it stops resolving — scanners see an inactive page) or reactivate it. Free plan allows up to 3 active codes."New value: +"Pause the code (it stops resolving — scanners see an inactive page) or reactivate it. Free plan allows up to 1 active code."

Changed3 schema fields changedAug 31, 2026

addedInput schema / properties / android_destination

Added value: +{
+  "description": "App links: Android scanners follow this http(s) URL instead of destination (e.g. the Google Play page). Pass null to clear.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / ios_destination

Added value: +{
+  "description": "App links: iOS scanners follow this http(s) URL instead of destination (e.g. the App Store page). Pass null to clear. Applies to the plain redirect only.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / pause_until

Added value: +{
+  "description": "ISO 8601 timestamp: schedule a pause until then (scanners see the inactive page; the code self-resumes at the deadline). Pass null to clear the schedule. Future timestamps only, active codes only.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed3 schema fields changedAug 6, 2026

addedInput schema / properties / lock_hint

Added value: +{
+  "description": "Optional hint shown on the unlock page, e.g. \"Ask at the bar\". Max 60 characters.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / password

Added value: +{
+  "description": "Pro: require this password before the code redirects (min 4 characters). Pass null to remove all protection.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / pin

Added value: +{
+  "description": "Pro: require a 4-digit PIN before the code redirects. Exactly 4 digits. Pass null to remove all protection.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedAug 5, 2026

addedInput schema / properties / status

Added value: +{
+  "description": "Pause the code (it stops resolving — scanners see an inactive page) or reactivate it. Free plan allows up to 3 active codes.",
+  "enum": [
+    "active",
+    "paused"
+  ],
+  "type": "string"
+}

First observedJun 27, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does mention the auth requirement and the partial-update semantics, which are helpful. However, it doesn't disclose potential side effects (e.g., whether changing status pauses the code immediately, or what happens to existing fields not passed beyond the implied retention). It also lacks information about rate limits or reversibility. For a mutation tool, this is adequate but not rich.

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 two sentences with zero waste. It front-loads the core purpose and then gives the partial-update guidance and auth requirement. Every sentence earns its place.

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 has 14 parameters and no output schema, the description is thin. It covers the auth requirement and the partial-update behavior, but omits return value details (though no output schema exists), error handling, and any prerequisites (e.g., the code must exist). It also doesn't mention any consequences of pausing or scheduling. For a tool this complex, more context would help an agent avoid mistakes.

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 baseline is 3. The description merely lists the editable fields (destination, label, slug, tags, folder) without adding meaning beyond what the schema already provides (e.g., constraints, null semantics). It adds little extra value for parameter comprehension.

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 states a clear verb and resource: 'Edit a dynamic QR code' and lists the editable fields (destination, label, slug, tags, folder). This distinguishes it from sibling tools like create_dynamic_qr and delete_dynamic_qr, though it doesn't explicitly name those alternatives. It's unambiguous about the operation.

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 phrase 'Pass only the fields you want to change' implies partial updates, which is useful guidance. It also mentions the API key requirement. However, it does not explicitly state when to use this tool vs alternatives (e.g., when to use bulk_create_dynamic_qr instead), nor does it provide exclusions or prerequisites beyond authentication.

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

All OpenQR tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?