Skip to main content
Glama
Sign In

PixelFlow

by so.pixelflow
OverviewDiscussionsAdmin

Get dashboard link

get_connect_link

Create a one-time link to the PixelFlow dashboard page for a step that needs a browser sign-in or a secret. Returns the link and when it expires. The link holds only an opaque id and works only for this user when signed in, so no credential passes through the chat. It must be opened in a regular browser such as Chrome, Safari, or Firefox. Integration and Visual Tagger targets are refused until site setup has passed verify. Use it when connecting an ad platform pixel (such as Facebook or TikTok), connecting an integration (such as Stripe or Calendly), opening billing, or opening the Visual Tagger on a page of the site. A Visual Tagger link saves the trigger itself when the user confirms, so read list_triggers afterwards instead of calling create_trigger.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>",
      "target": "<target>"
    },
    "name": "get_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesDashboard page to open. ad_platform: connect or reconnect a pixel. integration: connect an integration. billing: change the plan. visual_tagger: pick an element on page_path to track.
site_idYesSite to act on, as returned by list_sites.
page_pathNoPath on this site, such as /thank-you. Any query string is dropped.
ad_platformNoAd platform to connect, such as facebook or tiktok. Names are in list_supported_values's `ad_platforms`.
integrationNoIntegration to connect, such as stripe or calendly. Names are in list_supported_values's `integrations`.

Output Schema

NameRequiredDescriptionDefault
urlYesOne-time dashboard link.
targetYesDashboard page the link opens.
site_idYesSite id.
page_pathNovisual_tagger only: page the Visual Tagger opens.
expires_atYesWhen the link stops working.
ad_platformNoad_platform only: ad platform the link connects, such as facebook.
integrationNointegration only: integration the link connects, such as stripe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / ad_platform
      Added value: +{
+  "description": "Ad platform to connect, such as facebook or tiktok. Names are in list_supported_values's `ad_platforms`.",
+  "type": "string"
+}
    • addedInput schema / properties / integration
      Added value: +{
+  "description": "Integration to connect, such as stripe or calendly. Names are in list_supported_values's `integrations`.",
+  "type": "string"
+}
    • changedInput schema / properties / page_path / description
      Previous value: -"Path on this Site for visual_tagger, such as /thank-you. A query is dropped"New value: +"Path on this site, such as /thank-you. Any query string is dropped."
    • removedInput schema / properties / site
      Removed value: -{
-  "description": "Domain, id, or external id from list_sites",
-  "type": "string"
-}
    • addedInput schema / properties / site_id
      Added value: +{
+  "description": "Site to act on, as returned by list_sites.",
+  "type": "integer"
+}
    • changedInput schema / properties / target / description
      Previous value: -"Ad Platform name (meta, facebook, tiktok, or a later catalog name), billing, stripe, calendly, or visual_tagger"New value: +"Dashboard page to open. ad_platform: connect or reconnect a pixel. integration: connect an integration. billing: change the plan. visual_tagger: pick an element on page_path to track."
    • addedInput schema / properties / target / enum
      Added value: +[
+  "ad_platform",
+  "integration",
+  "billing",
+  "visual_tagger"
+]
    • changedInput schema / required
      Previous value: -[
-  "site",
-  "target"
-]New value: +[
+  "site_id",
+  "target"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "ad_platform": {
+      "description": "ad_platform only: ad platform the link connects, such as facebook.",
+      "type": "string"
+    },
+    "expires_at": {
+      "description": "When the link stops working.",
+      "format": "date-time",
+      "type": "string"
+    },
+    "integration": {
+      "description": "integration only: integration the link connects, such as stripe.",
+      "type": "string"
+    },
+    "page_path": {
+      "description": "visual_tagger only: page the Visual Tagger opens.",
+      "type": "string"
+    },
+    "site_id": {
+      "description": "Site id.",
+      "type": "integer"
+    },
+    "target": {
+      "description": "Dashboard page the link opens.",
+      "enum": [
+        "ad_platform",
+        "integration",
+        "billing",
+        "visual_tagger"
+      ],
+      "type": "string"
+    },
+    "url": {
+      "description": "One-time dashboard link.",
+      "format": "uri",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "target",
+    "site_id",
+    "expires_at"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the link is one-time, expires, contains only an opaque id, works only for the signed-in user, and must be opened in a regular browser. It also notes that credentials do not pass through chat and that Visual Tagger links save the trigger themselves, which is important behavioral context.

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 front-loaded with the core action and return behavior, followed by security constraints, preconditions, use cases, and the Visual Tagger warning. Every sentence adds operational value, and no sentence is repetitive or wasted.

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

Completeness5/5

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

For a tool with five parameters, an output schema, and simple annotations, the description covers purpose, constraints, use cases, browser requirements, verification prerequisites, and a key sibling interaction. It gives the agent enough context to select and invoke the tool correctly.

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 schema already documents target, site_id, page_path, ad_platform, and integration. The description reinforces target use cases with examples such as Facebook, TikTok, Stripe, and Calendly, but it does not add much conditional parameter guidance beyond what the schema already provides.

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 states a specific verb and resource: create a one-time link to the PixelFlow dashboard page for a browser sign-in or secret. It also explains what the link is for and what it returns, making the tool distinguishable from siblings like create_trigger and list_triggers.

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

Usage Guidelines5/5

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

It explicitly lists when to use the tool: connecting an ad platform pixel, connecting an integration, opening billing, or opening Visual Tagger. It also states a prerequisite for Integration and Visual Tagger targets and redirects the agent to list_triggers after a Visual Tagger confirmation instead of calling create_trigger.

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

All PixelFlow toolsInspect
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