Read

get_guidance

Returns Outli.ne's canonical build guide — goal→structure templates, section grammar by creator type, free vs Pro card kinds, and the recommended create→curate→optimize loop — so an agent builds profiles with platform best practices instead of guessing.

Parameters

This tool takes no parameters. Pass an empty object {} or omit args entirely.

Name	Type	Required	Description
No parameters

Response

Field	Type	What it means
overview	string	Outli’ne business context (platform description, target audience, primary keywords) — the same grounding text the autobuild AI uses. Good to include verbatim in agent system prompts for consistent voice.
principles	string[]	Cardinal rules for profile building: voice fidelity, photo covers on every card, CTA placement, template selection, and a reminder to call get_taste_fingerprint first. Treat as hard constraints.
templates	Array<{id:string, goalLabel:string, goalDescription:string, stacks:Array<{title:string, cardKinds:string[]}>}>	Three goal-primary structural templates: t1-get-booked (service providers), t3-show-portfolio (photographers/artists), t5-general (fallback). Each defines recommended stack titles and ordered card kinds. Pick the template whose goalDescription matches the creator’s objective before calling add_stack/add_card.
cardKinds	{free:string[], pro:string[]}	Complete card-kind catalogue split by entitlement tier. free: basic, about, link, portfolio, service, testimonial. pro: contact, book-me, embed-booking, buy, email. Attempting add_card with a pro kind on a free account will be rejected at the write layer.
sectionGrammarByCreatorType	Record<string, string>	Per-creator-type prose guidance on stack titles and card copy style. Keys are the four detection buckets: ‘photographer’, ‘beauty_wellness’, ‘service_booking’, ‘other’. Use the matching key when naming stacks and writing headings.
loop	string[]	Ordered 7-step create→curate→optimize workflow as a numbered string array. Use as a session checklist: get_guidance → get_taste_fingerprint → import → build → set_social/seo → publish → analytics.

Example

Request

json

{}

Response

json

{
  "overview": "Outli.ne is a mobile-first...",
  "principles": [
    "Stay in the creator's voice...",
    "Every card should have a photo cover...",
    "Put the primary CTA on the lead card..."
  ],
  "templates": [
    {
      "id": "t1-get-booked",
      "goalLabel": "Get Booked",
      "goalDescription": "Service providers who...",
      "stacks": [
        {
          "title": "Work With Me",
          "cardKinds": ["service", "book-me"]
        }
      ]
    }
  ],
  "cardKinds": {
    "free": [
      "basic", "about", "link",
      "portfolio", "service", "testimonial"
    ],
    "pro": [
      "contact", "book-me",
      "embed-booking", "buy", "email"
    ]
  },
  "sectionGrammarByCreatorType": {
    "photographer": "Use evocative stack...",
    "beauty_wellness": "Lead with transformation...",
    "service_booking": "Lead with outcome...",
    "other": "Mirror the creator's..."
  },
  "loop": [
    "1. get_guidance — start here",
    "2. get_taste_fingerprint",
    "3. import_from_instagram / import_from_url",
    "4. add_stack / add_card / update_card",
    "5. set_social_links / set_seo",
    "6. publish",
    "7. get_analytics + log_curation_decision"
  ]
}

When to use

Call this as the very first tool in any build or curation session — before reading the creator's taste fingerprint, importing media, or writing a single card — so the agent is grounded in Outli.ne's structure templates, voice rules, and card-kind entitlements. Re-calling mid-session is unnecessary since the payload is static and cached server-side.

Gotchas

Watch out

Takes no parameters — pass an empty object {} or omit args entirely; the input schema is {} and any keys sent are ignored.
The response is process-cached after the first call per warm server instance — subsequent calls in the same session return the identical object with zero I/O, so redundant calls are safe but wasteful.
cardKinds.pro tells you what exists, not what the current account can use — attempting add_card with a pro kind on a free account will fail at the write layer, not here.
Call this BEFORE get_taste_fingerprint — the loop field inside the response documents the correct order; reversing them means proposing structure without platform grounding first.

← All tools ← MCP Guide