WisePPC

get_session_context

Read-onlyIdempotent

Start here; no arguments. Overview: your business, connected accounts with target ids (kind:account[:unit]), names, marketplaces and currencies; key_grants; preferences; tool-surface version and changes since your last session. target: that Ads profile's primer (own pending actions, recent changes, benchmarks, runbooks, gotchas). section: accounts (all, paged), preferences, grants (each unit's write ops and modes), business_profiles (list), webhooks.

Input Schema

Name	Required	Description
`limit`	No	Accounts page size.
`offset`	No	Accounts rows to skip.
`target`	No	From get_session_context targets: kind:account[:unit].
`section`	No	Default overview. business_profiles: OAuth is fixed to one business.
`category`	No	Preferences category.
`destinationId`	No	One linked webhook.
`include_benchmarks`	No	Primer benchmarks.
`recent_changes_days`	No	Primer window, days.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedNov 2, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / businessProfileId

Removed value: -{
-  "description": "Business profile ID. Optional if a session default is selected.",
-  "type": [
-    "integer",
-    "string"
-  ]
-}

addedInput schema / properties / category

Added value: +{
+  "description": "Preferences category.",
+  "enum": [
+    "display",
+    "analysis",
+    "alerts",
+    "targets",
+    "defaults",
+    "general"
+  ],
+  "type": "string"
+}

addedInput schema / properties / destinationId

Added value: +{
+  "description": "One linked webhook.",
+  "format": "uuid",
+  "type": "string"
+}

changedInput schema / properties / include_benchmarks / description

Previous value: -"Include the 180-day account ACoS / spend block. Default true. false skips the extra ClickHouse query (~150ms)."New value: +"Primer benchmarks."

addedInput schema / properties / limit

Added value: +{
+  "description": "Accounts page size.",
+  "type": [
+    "integer",
+    "string"
+  ]
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Accounts rows to skip.",
+  "type": [
+    "integer",
+    "string"
+  ]
+}

removedInput schema / properties / profileId

Removed value: -{
-  "description": "Advertising account ID. Required. Accepts integer or numeric string (MCP clients serialize large int64 values as strings to preserve precision past Number.MAX_SAFE_INTEGER).",
-  "type": [
-    "integer",
-    "string"
-  ]
-}

changedInput schema / properties / recent_changes_days / description

Previous value: -"Window in days for the recent_campaign_changes block. Default 7. Clamped to [1, 90]."New value: +"Primer window, days."

addedInput schema / properties / section

Added value: +{
+  "description": "Default overview. business_profiles: OAuth is fixed to one business.",
+  "enum": [
+    "overview",
+    "accounts",
+    "preferences",
+    "grants",
+    "business_profiles",
+    "webhooks"
+  ],
+  "type": "string"
+}

addedInput schema / properties / target

Added value: +{
+  "description": "From get_session_context targets: kind:account[:unit].",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "profileId"
-]
```

First observedOct 18, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuine behavioral context: it returns 'changes since your last session' and a target primer with pending actions, runbooks, and gotchas. That disclosure of what the call yields goes beyond the annotations, though it does not discuss pagination behavior or response shape granularly.

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?

It is tightly front-loaded with 'Start here; no arguments' and then a compact enumeration keyed by selector. A few terms ('key_grants', 'tool-surface version') are cryptic jargon that cost a little clarity, but overall every clause carries 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 an 8-parameter, zero-required orientation tool with no output schema, the description effectively conveys the return structure by enumerating what overview, target, and each section provide. It leaves fine-grained detail (paging mechanics, exact response fields) to the schema, which is acceptable given no output schema but keeps it from a 5.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds meaning beyond the enum labels: target is 'kind:account[:unit]' and represents a profile primer, grants returns each unit's write ops and modes, accounts is 'all, paged'. It stops short of explaining limit/offset/category/destinationId explicitly, relying on the schema for those.

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 tool is clearly the entry-point/orientation tool ('Start here; no arguments') and it enumerates the concrete resources it surfaces: business, connected accounts with target ids, grants, preferences, and tool-surface version. It reads as a session-context loader rather than restating the name. It never differentiates itself explicitly from siblings, keeping it from a 5.

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

Usage Guidelines4/5

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

'Start here' is a strong, explicit first-use directive, and the per-selector notes (target, section) tell an agent how to route once inside. There is no explicit statement of when NOT to use it or a named sibling alternative, which caps it below a 5.

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

All WisePPC 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?