← WebMCP Directory

reloadium.com

reloadium.com

live Unverified (seed import) AI & Agents 204 tools imperative implementation

Paste a topic, URL, or PDF/TXT/MD — get a multi-episode AI podcast with audio, transcripts, timelines and quizzes. 60+ languages.

First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com

Answer 67 · Act 127 · Transact 10 · Score: Not yet scored

Tool inspector

generateOptimizedResume

act imperative

Generate a clean, single-column, ATS-safe resume PDF from the user's real background and show it in chat. Renders via the exact same engine as generatePdf (single column, standard section headers, one embedded Unicode font, no tables/columns/text-boxes/icons) since those are precisely the layout patterns that break real ATS parsers (Workday, Greenhouse, iCIMS, Lever) — you don't need to think about formatting, just supply clean structured content. If the user gives you a job posting URL, call getPageMarkdown on it FIRST and use the real result — don't call this tool claiming to have tailored the resume to a posting you haven't actually fetched and read, that's a false claim even if the resume still looks reasonable. When there's a target role or job posting to tailor against, call useStrongerModel with {"stronger":true} before this tool: telling genuine tailoring apart from fabrication takes real judgment under pressure to match the posting's keywords, and getting it wrong here means a factually false resume, not just a formatting slip — the same trade-off useStrongerModel's own description asks you to weigh. A plain resume with no target role to match doesn't need it. Once there's a target role or job posting in this conversation (fetched via getPageMarkdown, or described by the user), tailor the summary and bullet wording to genuinely and naturally reflect that role's real terminology and priorities — but ONLY using the user's actual, already-known background; never invent skills, employers, titles, or achievements they haven't told you about. This includes the skills[] list specifically: only put a technology/skill there if the source material explicitly says the person has used, studied, or worked with it — inferring a specific unlisted technology from a same-domain but different thing (e.g. listing 'Go' because they took a 'Performance Engineering' course, or 'SQL/MySQL' because the target role wants it and they mention 'databases' generically) is fabrication,…

Page: /

Input schema

PropertyTypeRequiredDescription
fullName string yes —
contactLine string yes One line: email • phone • city, country • linkedin/portfolio URL — whatever the user actually gave you.
targetRole string no The role/job posting this is tailored for, if any — for your own context when writing summary/bullets, not necessarily rendered verbatim.
summary string no Optional 2-4 sentence professional summary, tailored to targetRole if given.
experience array yes —
education array no —
skills array yes Flat list of real skills the user actually has — matched to the target role's terminology where genuinely applicable, not padded.
sourceSkills array no extractInfoFromCV's own skills[] output, passed through unmodified — used to verify skills[] above doesn't add anything not actually there. Omit only if you didn't extract from a CV (e.g. the user described their background directly in chat).
certifications array no —
Raw JSON schema
{
  "type": "object",
  "properties": {
    "fullName": {
      "type": "string"
    },
    "contactLine": {
      "type": "string",
      "description": "One line: email • phone • city, country • linkedin/portfolio URL — whatever the user actually gave you."
    },
    "targetRole": {
      "type": "string",
      "description": "The role/job posting this is tailored for, if any — for your own context when writing summary/bullets, not necessarily rendered verbatim."
    },
    "summary": {
      "type": "string",
      "description": "Optional 2-4 sentence professional summary, tailored to targetRole if given."
    },
    "experience": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "jobTitle": {
            "type": "string"
          },
          "company": {
            "type": "string"
          },
          "location": {
            "type": "string"
          },
          "startDate": {
            "type": "string",
            "description": "e.g. 'Jan 2020'"
          },
          "endDate": {
            "type": "string",
            "description": "e.g. 'Mar 2023' or 'Present'"
          },
          "bullets": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Achievement bullets — quantified where you genuinely know the numbers, never invented."
          }
        },
        "required": [
          "jobTitle",
          "company",
          "bullets"
        ]
      }
    },
    "education": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "degree": {
            "type": "string"
          },
          "institution": {
            "type": "string"
          },
          "location": {
            "type": "string"
          },
          "year": {
            "type": "string"
          }
        },
        "required": [
          "degree",
          "institution"
        ]
      }
    },
    "skills": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Flat list of real skills the user actually has — matched to the target role's terminology where genuinely applicable, not padded."
    },
    "sourceSkills": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "extractInfoFromCV's own skills[] output, passed through unmodified — used to verify skills[] above doesn't add anything not actually there. Omit only if you didn't extract from a CV (e.g. the user described their background directly in chat)."
    },
    "certifications": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "fullName",
    "contactLine",
    "experience",
    "skills"
  ]
}

Similar websites

api.lmm.best

api.lmm.best

Connect AI models, tools and applications with LMM Forge. Explore model access, developer guides and open-source collaboration.

live Unverified AI & Agents Transact tools
93 tools A43 / Act47 / T3 Not yet scored Seen 2026-11-05
lmm_signal_state lmm_signal_start lmm_signal_rotate lmm_signal_hint lmm_signal_records
Inspect tools
deskintab.dgkhan08.workers.dev

deskintab.dgkhan08.workers.dev

An operating system in your browser, where you and your AI agent share apps, files, and projects through WebMCP.

live Unverified AI & Agents Transact tools
89 tools A18 / Act70 / T1 Not yet scored Seen 2026-11-05
desktop_get_context desktop_reveal home_navigate projects_navigate tasks_navigate
Inspect tools
webmcp.agentsdesk.dev

webmcp.agentsdesk.dev

Meridian Ops

live Unverified AI & Agents Transact tools
83 tools A43 / Act24 / T16 Not yet scored Seen 2026-11-05
find_capabilities invoke_capability get_context get_action_status search_customers
Inspect tools
cesium-browser-agent.pages.dev

cesium-browser-agent.pages.dev

Cesium Agent Lab

live Unverified AI & Agents
61 tools A8 / Act53 / T0 Not yet scored Seen 2026-11-05
flyTo setView getView zoomToExtent saveViewpoint
Inspect tools

Related on Influzer