Skip to main content
Glama
benswel

QR for Agent

create_social_qr

Generate QR codes that link to multiple social media profiles. When scanned, the short URL returns a JSON object containing all platform links for easy access.

Instructions

Create a QR code that links to social media profiles. When scanned via the short URL, returns a JSON object with all platform links. Provide at least one platform link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
facebookNoFacebook profile/page URL.
instagramNoInstagram profile URL.
twitterNoTwitter/X profile URL.
linkedinNoLinkedIn profile URL.
youtubeNoYouTube channel URL.
tiktokNoTikTok profile URL.
githubNoGitHub profile URL.
websiteNoPersonal/company website URL.
labelNoLabel for this QR code.
formatNoImage format.svg
foreground_colorNoHex color for dots.
background_colorNoHex color for background.
dot_styleNoDot shape.
corner_styleNoCorner shape.
logo_urlNoLogo URL or data URI.
frame_styleNoFrame style around QR.
frame_textNoCTA text on frame (max 30 chars).
frame_colorNoFrame background color.
frame_text_colorNoFrame text color.

Implementation Reference

  • The handler function for 'create_social_qr' that sends a POST request to '/api/qr' with social media data.
    handler: async (input: Record<string, unknown>) => {
      const { facebook, instagram, twitter, linkedin, youtube, tiktok, github, website, ...rest } = input;
      return apiRequest("/api/qr", {
        method: "POST",
        body: { type: "social", social_data: { facebook, instagram, twitter, linkedin, youtube, tiktok, github, website }, ...rest },
      });
    },
  • The input schema definition for 'create_social_qr' using Zod, detailing required social profile links and QR code styling options.
    inputSchema: z.object({
      facebook: z.string().optional().describe("Facebook profile/page URL."),
      instagram: z.string().optional().describe("Instagram profile URL."),
      twitter: z.string().optional().describe("Twitter/X profile URL."),
      linkedin: z.string().optional().describe("LinkedIn profile URL."),
      youtube: z.string().optional().describe("YouTube channel URL."),
      tiktok: z.string().optional().describe("TikTok profile URL."),
      github: z.string().optional().describe("GitHub profile URL."),
      website: z.string().optional().describe("Personal/company website URL."),
      label: z.string().optional().describe("Label for this QR code."),
      format: z.enum(["svg", "png"]).default("svg").describe("Image format."),
      foreground_color: z.string().regex(/^#[0-9A-Fa-f]{6}$/).optional().describe("Hex color for dots."),
      background_color: z.string().regex(/^#[0-9A-Fa-f]{6}$/).optional().describe("Hex color for background."),
      dot_style: z.enum(["square", "rounded", "dots", "classy-rounded"]).optional().describe("Dot shape."),
      corner_style: z.enum(["square", "extra-rounded", "dot"]).optional().describe("Corner shape."),
      logo_url: z.string().optional().describe("Logo URL or data URI."),
      frame_style: z.enum(["none", "banner_bottom", "banner_top", "rounded"]).optional().describe("Frame style around QR."),
      frame_text: z.string().max(30).optional().describe("CTA text on frame (max 30 chars)."),
      frame_color: z.string().regex(/^#[0-9A-Fa-f]{6}$/).optional().describe("Frame background color."),
      frame_text_color: z.string().regex(/^#[0-9A-Fa-f]{6}$/).optional().describe("Frame text color."),
    }),
Behavior3/5

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

With no annotations provided, the description carries the full burden and adds valuable context about the scan behavior ('returns a JSON object with all platform links'), but omits other behavioral traits like persistence guarantees, error conditions, or rate limits.

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 sentences with zero waste: purpose statement first, behavioral disclosure second, input constraint third. Every sentence earns its place.

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 19-parameter tool with no output schema, the description adequately covers the unique domain aspects (social media aggregation, JSON response format) while appropriately delegating visual customization details to the well-documented schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema description coverage (baseline 3), the description adds critical semantic constraints not captured in the schema—that at least one platform link must be provided—even though the schema marks all 19 parameters as optional.

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

Purpose5/5

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

The description opens with a specific verb ('Create') and resource ('QR code') scoped to 'social media profiles', clearly distinguishing it from sibling tools like create_email_qr or create_wifi_qr.

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 provides a constraint ('Provide at least one platform link') but does not explicitly state when to use this tool versus the generic create_qr_code or alternatives, relying on the specific domain to imply 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

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/benswel/qr-agent-core'

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